BLACKOUT MAP

Linux · Kernel

CVE-2026-53266

netfilter: bridge: make ebt_snat ARP rewrite writable

Bei Angriffen ausgenutzt Hoch 8,8 Angriffswahrscheinlichkeit: 0,9%
Teilen

Was es ist

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().

CISA: 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.

Was zu tun ist

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.

Frist für US-Bundesbehörden: 21. September 2026

Zur CISA-Liste hinzugefügt
18. September 2026
Veröffentlicht
25. Juni 2026
Schweregrad
Hoch 8,8 CVSS 3.1
Wahrscheinlichkeit von Angriffen in den nächsten 30 Tagen (EPSS)
0,9% unter den obersten 39,4% aller bekannten Schwachstellen
Schwachstellentyp
CWE-787
Mehr Details
NVD · CVE.org · CISA
Alle Quellen (8)

Weitere ausgenutzte Schwachstellen von Linux

HinzugefügtSchwachstelleProduktSchweregradAngriffswahrscheinlichkeit
18.09.2026Improper Check for Unusual or Exceptional ConditionsCVE-2025-39682KernelKritisch 9,83,3%
18.09.2026Race ConditionCVE-2025-39964KernelHoch 7,81,6%
27.08.2026UnspecifiedCVE-2026-53362KernelHoch 7,80,7%
26.08.2026Out-of-Bounds WriteCVE-2022-0995KernelHoch 7,88,9%
02.06.2026Improper AuthenticationCVE-2022-0492KernelHoch 7,85,5%
01.05.2026Incorrect Resource Transfer Between SpheresCVE-2026-31431KernelHoch 7,898%
26.01.2026Integer OverflowCVE-2018-14634KernelHoch 7,815%
06.10.2025Heap Out-of-Bounds WriteCVE-2021-22555KernelHoch 8,379%

Alle →

Quellen: Known Exploited Vulnerabilities (CISA, gemeinfrei), CVE records (cve.org) und EPSS (FIRST). Die Angriffswahrscheinlichkeit ist die EPSS-Schätzung, dass jemand in den nächsten 30 Tagen versucht, die Schwachstelle auszunutzen.