CVE-2026-53266

netfilter: bridge: make ebt_snat ARP rewrite writable

HIGH
8.8
CVSS Score
Published: June 25, 2026 at 08:39 AM UTC
Updated: September 19, 2026 at 04:17 AM 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
HIGH8.8
Exploitation
CISA KEV
Exploit prediction
EPSS 0.9%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score0.9%

EPSS (Exploit Prediction Scoring System) estimates a 0.9% chance this CVE is exploited in the wild within the next 30 days — higher than 61% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Linux Kernel contains an out-of-bounds write vulnerability in the ebtables SNAT target which allows an ARP sender hardware address rewrite to write directly into a nonlinear socket-buffer fragment backed by a splice-imported file page. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.

Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Ransomware Use
Unknown
Added to KEV
Sep 18, 2026
Remediation Due
Sep 21, 2026
44 days overdue

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: make ebt_snat ARP rewrite writable The ebtables SNAT target keeps the Ethernet source address rewrite behind skb_ensure_writable(skb, 0). This is intentional: at the bridge ebtables hooks the Ethernet header is addressed through skb_mac_header()/eth_hdr(), while skb->data points at the Ethernet payload. Asking skb_ensure_writable() for ETH_HLEN bytes would check the payload, not the Ethernet header, and would reintroduce the small packet regression fixed by commit 63137bc5882a. However, the optional ARP sender hardware address rewrite is different. It writes through skb_store_bits() at an offset relative to skb->data: skb_store_bits(skb, sizeof(struct arphdr), info->mac, ETH_ALEN) skb_header_pointer() only safely reads the ARP header; it does not make the later sender hardware address range writable. If that range is still held in a nonlinear skb fragment backed by a splice-imported file page, skb_store_bits() maps the frag page and copies the new MAC address directly into it. Ensure the ARP SHA range is writable before reading the ARP header and before calling skb_store_bits().

Affected

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

v ≥ 5.4.73v ≥ 5.8.17v ≥ 5.9.25.10 ≤ v < 5.10.2595.10 ≤ v < 5.15.2105.10 ≤ v < 6.1.1765.10 ≤ v < 6.12.945.10 ≤ v < 6.18.365.10 ≤ v < 6.6.1435.10 ≤ v < 7.0.135.10 ≤ v < 7.15.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1765.4.73 ≤ v < 5.55.8.17 ≤ v < 5.95.9.2 ≤ v < 5.105.9.2 ≤ v < 5.10.2596.13 ≤ v < 6.18.366.19 ≤ v < 7.0.136.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.942f3839075a5f8dcf116c1abe35b36b018ac624455.4.735.8.175.9.251ba2945a8ef65ae437c8f9ba05f0343aa82ae5b63137bc5882a1882c553d389fdeeeace86ee17417.1 rc17.1 rc27.1 rc37.1 rc47.1 rc57.1 rc6b7d23c2c87584eb429f115c078ed511be8b18e29
Vendor states this is fixed in 153ea96c806aea395daba907a4f88480b6ad5093 (fixed)
Vendor states this is fixed in 67ba971ae02514d85818fe0c32549ab4bfa3bf49 (fixed)
Vendor states this is fixed in 76280b78cc9f23bdc6438e10ad6dff148ef8375b (fixed)
Vendor states this is fixed in afd64b59c3de9bbbdd3759e834fdc55cda716e0b (fixed)
Vendor states this is fixed in b18675263db1147c8e1cab625400c13a0d87bd2d (fixed)
Vendor states this is fixed in b7e91939ba9be805a62a257fa4e227dffbb88fa0 (fixed)
Vendor states this is fixed in bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87 (fixed)
Vendor states this is fixed in c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5 (fixed)
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.9, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.94 (unaffected)
Vendor states this is fixed in 6.18.36 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.13 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

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

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfoCWE-787

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