Home › Vulnerabilities

Linux Kernel: Exploited Flaw CVE-2026-53266

Published October 25, 2026 · Last updated October 25, 2026

Linux Linux Kernel CVE KEV Patch

What happened: On September 18, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-53266, a flaw in Linux Kernel, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "Linux Kernel Out-of-Bounds Write Vulnerability."

CISA's summary: "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."

What the National Vulnerability Database says

NVD first published CVE-2026-53266 on June 25, 2026. Its description, from the record's source (416baaa9-dc9f-4396-8d5f-8c081fb06d67), reads: "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()."

How serious is CVE-2026-53266?

The CVSS 3.1 base score is 8.8 out of 10 (High), scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67. In plain terms: an attacker can reach the Kernel weakness only with local access to the system; the attacker needs a low-privilege account; no one has to click or open anything. The listed impact on Kernel data secrecy is high, on data integrity high, and on availability high. The full vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Which Kernel versions are affected?

The CVE record lists these affected ranges:

  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, 76280b78cc9f23bdc6438e10ad6dff148ef8375b
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, b7e91939ba9be805a62a257fa4e227dffbb88fa0
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, afd64b59c3de9bbbdd3759e834fdc55cda716e0b
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, 153ea96c806aea395daba907a4f88480b6ad5093
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, b18675263db1147c8e1cab625400c13a0d87bd2d
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5
  • 63137bc5882a1882c553d389fdeeeace86ee1741 up to, but not including, 67ba971ae02514d85818fe0c32549ab4bfa3bf49

If your Kernel version falls in one of these ranges, check Linux's advisory for the fixed release that applies to you.

What kind of weakness is it?

CISA and NVD map CVE-2026-53266 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):

  • CWE-787: Out-of-bounds Write. MITRE's definition: "The product writes data past the end, or before the beginning, of the intended buffer."

CISA required action for CVE-2026-53266

CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "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."

Timeline for CVE-2026-53266

  • June 25, 2026: NVD publishes CVE-2026-53266.
  • September 18, 2026: CISA adds CVE-2026-53266 to the KEV catalog.
  • September 19, 2026: latest change to the NVD record (status: Analyzed).
  • September 21, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-53266.

Advisories and technical references

The NVD record for CVE-2026-53266 links to these references; tags in brackets are NVD's labels:

What to do

  • Run Linux Kernel? Follow Linux's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
  • Federal civilian agencies must act by September 21, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for Kernel too.
  • Ransomware use: CISA lists known ransomware campaign use for CVE-2026-53266 as "Unknown".
  • Don't run Kernel yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-53266" and asks for payment or remote access, that is a scam pattern, not a Linux alert.

CVE-2026-53266 record details from CISA and NVD

  • CISA forensic triage flag for CVE-2026-53266: Yes
  • Attack complexity for CVE-2026-53266: low
  • CVE-2026-53266 CVSS scope: changed
  • NVD sub-scores for CVE-2026-53266: exploitability 2.0, impact 6.0.
  • Who mapped the weakness type: 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary); [email removed] (Primary)
  • NVD product identifiers (CPE): cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* and 2 more
  • References in the NVD record: 9 (8 tagged Patch, 1 tagged US Government Resource).
  • CISA SSVC decision points for CVE-2026-53266 (from NVD): exploitation=active; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.