CVE-2026-52927

netfilter: ebtables: fix OOB read in compat_mtw_from_user

HIGH
7.8
CVSS Score
Published: June 24, 2026 at 07:14 AM UTC
Updated: October 19, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.34 ≤ v < 5.10.2595.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.356.19 ≤ v < 7.0.126.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.937.17.1 rc17.1 rc27.1 rc37.1 rc47.1 rc581e675c227ec60a0bdcbb547dc530ebee23ff931
Vendor states this is fixed in 21af4c030567d2e6c89bb927bc18b51fba52a400 (fixed)
Vendor states this is fixed in 7ad0e463fc7eafae2141cc38054264636f8b3e94 (fixed)
Vendor states this is fixed in a27cb7325a6c69970041c7f8541fafed5a1ea3ec (fixed)
Vendor states this is fixed in bf8e8eac7ede51dc318e06acef5a896dcbba7595 (fixed)
Vendor states this is fixed in d7a8fb6f10d55a1c37b0bf8c20cca24dffd76e00 (fixed)
Vendor states this is fixed in dad9ebf8107955bb54bd3f9cf22591b6ff37bac1 (fixed)
Vendor states this is fixed in f438d1786d657d57790c5d138d6db3fc9fdac392 (fixed)
Vendor states this is fixed in fcc4c043d137e7f1de4673dba1f3116e45377c67 (fixed)
Vendor states this is fixed in 2.6.34 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card