netfilter: ebtables: fix OOB read in compat_mtw_from_user
- 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.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: fix OOB read in compat_mtw_from_user Luxiao Xu says: The function compat_mtw_from_user() converts ebtables extensions from 32-bit user structures to kernel native structures. However, it lacks proper validation of the user-supplied match_size/target_size. When certain extensions are processed, the kernel-side translation logic may perform memory accesses based on the extension's expected size. If the user provides a size smaller than what the extension requires, it results in an out-of-bounds read as reported by KASAN. This fix introduces a check to ensure match_size is at least as large as the extension's required compatsize. This covers matches, watchers, and targets, while maintaining compatibility with standard targets. AFAIU this is relevant for matches that need to go though match->compat_from_user() call. Those that use plain memcpy with the user-provided size are ok because the caller checks that size vs the start of the next rule entry offset (which itself is checked vs. total size copied from userspace). The ->compat_from_user() callbacks assume they can read compatsize bytes, so they need this extra check. Based on an earlier patch from Luxiao Xu.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in d7a8fb6f10d55a1c37b0bf8c20cca24dffd76e00; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in 21af4c030567d2e6c89bb927bc18b51fba52a400; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in dad9ebf8107955bb54bd3f9cf22591b6ff37bac1; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in a27cb7325a6c69970041c7f8541fafed5a1ea3ec; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in 7ad0e463fc7eafae2141cc38054264636f8b3e94; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in bf8e8eac7ede51dc318e06acef5a896dcbba7595; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in fcc4c043d137e7f1de4673dba1f3116e45377c67; From 81e675c227ec60a0bdcbb547dc530ebee23ff931 · fixed in f438d1786d657d57790c5d138d6db3fc9fdac392
- Linux Linux
2.6.34
- KernelLinux
From 2.6.34 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.93; From 6.13.0 · fixed in 6.18.35; From 6.19.0 · fixed in 7.0.12
References 8
git.kernel.org
- stable/c/d7a8fb6f10d55a1c37b0bf8c20cca24dffd76e00
- stable/c/21af4c030567d2e6c89bb927bc18b51fba52a400
- stable/c/dad9ebf8107955bb54bd3f9cf22591b6ff37bac1
- stable/c/a27cb7325a6c69970041c7f8541fafed5a1ea3ec
- stable/c/7ad0e463fc7eafae2141cc38054264636f8b3e94
- stable/c/bf8e8eac7ede51dc318e06acef5a896dcbba7595
- stable/c/fcc4c043d137e7f1de4673dba1f3116e45377c67
- stable/c/f438d1786d657d57790c5d138d6db3fc9fdac392