Advisory

CVE-2026-53266: Linux Kernel Out-of-Bounds Write in ebtables SNAT ARP Rewrite (CVSS 8.8)

A high-severity out-of-bounds write flaw in the Linux kernel's netfilter bridge ebtables SNAT target allows a low-privileged local user to corrupt memory by triggering an ARP sender hardware address rewrite into a nonlinear socket-buffer fragment backed by a splice-imported file page. Successful exploitation can result in full confidentiality, integrity, and availability loss with impact potentially escaping the initial security boundary.

TL;DR: Apply all available vendor-supplied kernel patches immediately; if the affected kernel version is end-of-life and no patch is available, migrate to a supported kernel version in accordance with CISA KEV Required Action guidance and BOD 26-04.

What Is the Vulnerability?

CVE-2026-53266 is an out-of-bounds write (CWE-787) in the Linux kernel's netfilter bridge layer, specifically inside the ebt_snat target used by ebtables. The flaw resides in the optional ARP sender hardware address (SHA) rewrite path.

During normal operation at a bridge ebtables hook, the Ethernet header is accessed via skb_mac_header() / eth_hdr(), while skb->data points at the Ethernet payload. The existing guard call skb_ensure_writable(skb, 0) intentionally requests zero bytes of payload writability to avoid a regression with small packets; it does not make the ARP payload range writable.

The problematic code path calls skb_header_pointer() to read the ARP header and then writes the new MAC address via:

  • skb_store_bits(skb, sizeof(struct arphdr), info->mac, ETH_ALEN)

skb_header_pointer() provides a safe read of the ARP header but does not guarantee that the sender hardware address range immediately following it is writable. If that range resides in a nonlinear socket-buffer fragment backed by a splice-imported file page, skb_store_bits() maps the fragment page and copies the new MAC address directly into it — an out-of-bounds write into memory the kernel does not own for this purpose.

The fix, as described in the NVD advisory, ensures the ARP SHA range is made writable before reading the ARP header and before calling skb_store_bits().

Who and What Is Affected?

The vulnerability affects the Linux Kernel. Any system running a vulnerable kernel version that:

  • Operates as a network bridge using ebtables with an SNAT rule that rewrites ARP sender hardware addresses, and
  • Processes ARP traffic across that bridge where socket buffers may contain nonlinear fragments backed by splice-imported file pages

is potentially exposed to this flaw.

The CISA KEV entry notes that impacted products could be end-of-life (EoL) or end-of-service (EoS), meaning vendor-supported patches may not exist for all affected versions. This makes the exposure especially urgent for environments running older kernel branches.

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) indicates:

  • Local access is required (Attack Vector: Local)
  • Low complexity and low privileges are sufficient
  • No user interaction is needed
  • The scope changes — impact can extend beyond the vulnerable component

Potential Impact

With a CVSS base score of 8.8 (HIGH), this vulnerability carries serious consequences if exploited. The scope-change (S:C) in the vector indicates that exploitation may allow an attacker to affect resources beyond the security scope of the vulnerable component itself.

Impact CategoryRatingMeaning
ConfidentialityHighSensitive kernel or file-page data may be disclosed
IntegrityHighMemory contents can be overwritten, corrupting data or control flow
AvailabilityHighKernel crash or instability is possible

In practice, an out-of-bounds write into a splice-imported file page could corrupt file data in the page cache, destabilize the kernel, or be chained with other primitives toward privilege escalation. Because the vulnerability requires only low privileges and low complexity on a local system, the barrier to exploitation is relatively low once an attacker has any foothold on the host.

CISA has added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog (added 2026-09-18), confirming that exploitation has been observed in the wild.

What To Do Now

Act on the following steps in priority order:

  1. Identify exposure: Audit all Linux systems to determine which kernel versions are running. Focus first on systems acting as network bridges with ebtables SNAT rules that include ARP hardware address rewriting.
  2. Apply vendor patches: Apply all kernel security updates provided by your Linux distribution vendor (e.g., upstream kernel.org releases, or patches from your OS vendor's security advisory channel). Consult the vendor's own advisory for the specific patch commits addressing this flaw.
  3. Migrate off EoL kernels: Per CISA KEV Required Action guidance and BOD 26-04, if the running kernel version is end-of-life and no patch is available, discontinue use and transition to a supported kernel version. Running EoL software with a known exploited vulnerability is not an acceptable risk posture.
  4. Restrict local access: As a temporary mitigating control where patching is delayed, restrict who can obtain a local shell or low-privilege account on affected bridge hosts. This does not eliminate the vulnerability but raises the attacker's barrier slightly.
  5. Review ebtables rules: Where operationally feasible, audit and remove ebtables SNAT rules that perform ARP sender hardware address rewrites until the patch is applied. Eliminating the vulnerable code path removes the attack surface on that host.
  6. Monitor for indicators: Given that exploitation is confirmed per CISA KEV, review kernel logs and host-based telemetry for unusual kernel panics, memory corruption events, or anomalous bridge traffic patterns.

Primary references for patching guidance: CISA KEV Catalog, NVD CVE-2026-53266, and your Linux distribution vendor's security advisory.

How External Testing Can Surface Exposure

Because this vulnerability has a local attack vector, external network scanning alone cannot directly trigger or confirm exploitability. However, external and internal security testing can still help organizations understand and reduce their exposure:

  • Asset inventory and version fingerprinting: External and internal vulnerability scans that identify Linux kernel versions running on hosts can flag systems running versions known to be affected before the patch is confirmed as applied.
  • Configuration review: Automated or manual review of ebtables rule sets across bridge hosts can identify where the vulnerable SNAT ARP rewrite path is actively configured, narrowing the population of truly at-risk systems.
  • Patch verification: Post-patching authenticated scans or agent-based assessments can confirm that the kernel update has been successfully applied and that the system has been rebooted into the patched kernel — a step that is easy to overlook.
  • Attack surface mapping: Identifying which bridge hosts are reachable by low-privilege users (e.g., shared infrastructure, container hosts, virtual machine hypervisors) helps prioritize which systems face the greatest risk from a local exploitation scenario.

Organizations should not rely on perimeter controls alone as a substitute for patching, particularly given CISA's confirmation of active exploitation.

Sources & further reading: NVD CVE-2026-53266 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: git.kernel.org, git.kernel.org, git.kernel.org, git.kernel.org. This advisory contains no exploit code.

Frequently asked questions

Does an attacker need network access to exploit CVE-2026-53266?

No. The CVSS vector specifies a local attack vector (AV:L), meaning the attacker must have a local presence on the affected system — such as a low-privilege user account. Remote network access alone is not sufficient to directly exploit this vulnerability.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-53266 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-09-18, which indicates that exploitation has been observed. Organizations should treat this as an urgent remediation priority.

My kernel is end-of-life. What should I do if no patch is available?

CISA's KEV Required Action explicitly states that if mitigations are unavailable, users should discontinue use of the product and transition to a supported version. BOD 26-04 provides additional guidance on prioritizing security updates based on risk. Running an end-of-life kernel with a known exploited vulnerability is a critical operational risk.

Can I mitigate the risk without immediately patching by removing ebtables SNAT rules?

Removing or modifying ebtables SNAT rules to eliminate ARP sender hardware address rewrites would remove the specific code path where the out-of-bounds write occurs, reducing exposure on that host. However, this is a temporary operational workaround, not a fix. The only definitive remediation is applying the vendor-supplied kernel patch or migrating to a supported, patched kernel version.