netfilter: ip6t_rt: fix zero-address non-strict match out-of-bounds read
- 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.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 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: netfilter: ip6t_rt: fix zero-address non-strict match out-of-bounds read rt_mt6_check() permits rules to be configured with rtinfo->addrnr == 0 even when address matching (IP6T_RT_FST_MASK) is requested. In the IP6T_RT_FST_NSTRICT path, rt_mt6() evaluates packet routing addresses against rtinfo->addrs[i] and terminates backwards at the bottom of the loop: if (ipv6_addr_equal(ap, &rtinfo->addrs[i])) { i++; } if (i == rtinfo->addrnr) break; When addrnr is 0, if the first packet address matches rtinfo->addrs[0], i is incremented to 1. Because i is now strictly greater than addrnr (0), the loop termination condition (i == rtinfo->addrnr) is bypassed and will never be satisfied. If a crafted IPv6 packet contains matching routing addresses, i will advance past IP6T_RT_HOPS (16). The subsequent call to ipv6_addr_equal() reads beyond struct ip6t_rt, triggering UBSAN/KASAN out-of-bounds warnings or kernel panics. Fix this by: 1. Rejecting rules in rt_mt6_check() where IP6T_RT_FST_MASK is set but rtinfo->addrnr is zero. 2. In rt_mt6(), moving the termination condition (i < rtinfo->addrnr) into the for-loop header condition and removing the backwards break at the end of the loop body.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 959d1829d1ce8b91b435b24a923b51bcc8897090; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in fe336bab13834394320997de8b16ca4a913b4f13; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5a54f8b7f7fe207a5c14713015a5820588faf1ad; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in b89249819a7d6698bed152feafd3bc6c08489d15; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in dd55c0ea87bf70e4e4b3b683acd29ef981335b26; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 191239b0939692e92459d8d32cad14247fa93f89; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in d9cf4ac6f326330e1fe4d95671d36a6ff3593f64; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 82313c169eddc02b1bf5ba6b427803e272d3ec42
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9
References 8
git.kernel.org
- stable/c/959d1829d1ce8b91b435b24a923b51bcc8897090
- stable/c/fe336bab13834394320997de8b16ca4a913b4f13
- stable/c/5a54f8b7f7fe207a5c14713015a5820588faf1ad
- stable/c/b89249819a7d6698bed152feafd3bc6c08489d15
- stable/c/dd55c0ea87bf70e4e4b3b683acd29ef981335b26
- stable/c/191239b0939692e92459d8d32cad14247fa93f89
- stable/c/d9cf4ac6f326330e1fe4d95671d36a6ff3593f64
- stable/c/82313c169eddc02b1bf5ba6b427803e272d3ec42