ipv4: stop PMTU walk when nexthop group shrinks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.224, 6.1.191, 6.6.160, 6.12.113, 6.18.57, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ipv4: stop PMTU walk when nexthop group shrinks Commit 7d3f3b4367f3 ("net: ipv4: Cache pmtu for all packet paths if multipath enabled") made __ip_rt_update_pmtu() update every path. For nexthop objects, fib_info_num_path() and fib_info_nhc() independently load nh->nh_grp. RCU protects each group's lifetime but does not make the loads observe the same group. If replacement shrinks the group after the loop accepts an index, fib_info_nhc() returns NULL and update_or_create_fnhe() dereferences it. A deterministic probe only widened the existing window between the real operations. On v7.2, an RTM_NEWNEXTHOP replacement published a one-member group after the PMTU reader accepted index 1 from a two-member group, producing: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: update_or_create_fnhe+0x45/0x15b0 Stop when the indexed path is absent. Groups are dense, so no later index exists in that snapshot. The same real-writer window completed 114,423 PMTU iterations without an oops with this check. A reproducer is available on request. Replacement requires CAP_NET_ADMIN in the network namespace. Where unprivileged user namespaces are permitted, a local user can obtain it in a new user and network namespace.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Linux Linux
From 5.15.179 · fixed in 5.15.224; From 6.1.129 · fixed in 6.1.191; From 6.6.79 · fixed in 6.6.160; From 6.12.16 · fixed in 6.12.113
- Linux Linux
6.13
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.57; fixed in 7.2.11
References 7
git.kernel.org
- stable/c/82d83eec893d8ae84f280aec44c60d9fdecc62b5
- stable/c/a411df69524f91fe3adb8f9544d33e701fc9732c
- stable/c/7fd60d3c9a1e1b11ef5f1643bbae78d91eae2f4a
- stable/c/c60d17d6dd61adc761ac6f65a008fefbc54cbf87
- stable/c/c6d670ac656badfd0e15355e07a13a6bdf3b69fd
- stable/c/f27483f9975b5065ff67054cc7eb8edac6083488
- stable/c/6619e01855e65ef35723685a557e3eb106f4ecf5