nexthop: fix IPv6 route referencing IPv4 nexthop
- 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.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, and 2 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: nexthop: fix IPv6 route referencing IPv4 nexthop syzbot reported a panic [1] [2]. When an IPv6 nexthop is replaced with an IPv4 nexthop, the has_v4 flag of all groups containing this nexthop is not updated. This is because nh_group_v4_update is only called when replacing AF_INET to AF_INET6, but the reverse direction (AF_INET6 to AF_INET) is missed. This allows a stale has_v4=false to bypass fib6_check_nexthop, causing IPv6 routes to be attached to groups that effectively contain only AF_INET members. Subsequent route lookups then call nexthop_fib6_nh() which returns NULL for the AF_INET member, leading to a NULL pointer dereference. Fix by calling nh_group_v4_update whenever the family changes, not just AF_INET to AF_INET6. Reproducer: AF_INET6 blackhole ip -6 nexthop add id 1 blackhole group with has_v4=false ip nexthop add id 100 group 1 replace with AF_INET (no -6), has_v4 stays false ip nexthop replace id 1 blackhole pass stale has_v4 check ip -6 route add 2001:db8::/64 nhid 100 panic ping -6 2001:db8::1 [1] https://syzkaller.appspot.com/bug?id=e17283eb2f8dcf3dd9b47fe6f67a95f71faadad0 [2] https://syzkaller.appspot.com/bug?id=8699b6ae54c9f35837d925686208402949e12ef3
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in ceffe81a0be92afc0cd1340bc8ca46559cce9bb4; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in 9c2d6770a5f4545a307eb66979bef7656a34d621; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in 6275796f22bb382f3e9aa58ed0b4ef7bdad78cb8; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in aaac3bed034239e1d75732211d9b05f30b0b4f35; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in ad85961004fd4bd2f31209ac4b07612c6cefb9e7; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in 613c8f4a501421dd258b07ea614205d4e16ec845; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in b3b7e850e1541f0520c4a12ec884255c30427ff6; From 7bf4796dd09984ad1612877a82d0d139c70ae27f · fixed in 29c95185ba32b621fbc3800fb86e7dc3edf5c2be
- Linux Linux
5.3
- KernelLinux
From 5.3.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.141; From 6.7.0 · fixed in 6.12.91; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10
References 8
git.kernel.org
- stable/c/ceffe81a0be92afc0cd1340bc8ca46559cce9bb4
- stable/c/9c2d6770a5f4545a307eb66979bef7656a34d621
- stable/c/6275796f22bb382f3e9aa58ed0b4ef7bdad78cb8
- stable/c/aaac3bed034239e1d75732211d9b05f30b0b4f35
- stable/c/ad85961004fd4bd2f31209ac4b07612c6cefb9e7
- stable/c/613c8f4a501421dd258b07ea614205d4e16ec845
- stable/c/b3b7e850e1541f0520c4a12ec884255c30427ff6
- stable/c/29c95185ba32b621fbc3800fb86e7dc3edf5c2be