ipvs: avoid out-of-bounds write in ip_vs_nat_icmp
- 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 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ipvs: avoid out-of-bounds write in ip_vs_nat_icmp Sashiko warns that local attacker can modify the packet while it is processed by IPVS. Some places read the IP ihl field multiple times which can cause out-of-bounds access. One such place is ip_vs_nat_icmp where we can write after the validated area. Fix it by providing ciph argument just like it is done for IPv6 and use ciph->len as offset to the embedded transport header. Modify some IPv4 header checks by reading the ihl field only once.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 3b8f79af0e98f27b932b0b416e9c52b692d31ff9; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 3c779b258c9c3c3567af68d4f45c2f751f35bd0e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in be65fa324640c7a95e30b146159a2be5cc73f22e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in a69a4b3fff5814d079beff9a1e9d369994b2ed47; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 243d0187ec4c3837b9b0004f18d1068e46115760; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 646922a0379496154e8c8faca4f8e2fd9100cacc
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.152; From 6.7.0 · fixed in 6.12.104; From 6.13.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9