CVE-2026-53266

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Linux Kernel. For every flaw being used in attacks, see Exploited flaws; for Linux’s, see Linux flaws being used in attacks.

CVE-2026-53266 is a security flaw in Linux Kernel, the core of Linux, which runs most servers, Android phones and many home routers. Attackers can corrupt memory in Linux Kernel, which they use to take it over. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 18 Sep 2026.[1]

Linux Kernel is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed by 8 commits to Linux, in the releases that include them.

Description

CISA calls it an out-of-bounds write in Linux Kernel. In its words: “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.”[1]

The CVE record adds: “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…”[2]

The underlying weakness is out-of-bounds write (CWE-787), in MITRE’s list of common software weaknesses.

It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]

ProductFixed in
Linuxcommit bf84ad7c7a9e
Linuxcommit 76280b78cc9f
Linuxcommit b7e91939ba9b
Linuxcommit afd64b59c3de
Linuxcommit 153ea96c806a
Linuxcommit b18675263db1
Linuxcommit c9b5ff59feff
Linuxcommit 67ba971ae025

Most families won’t have Linux Kernel; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 18 Sep 2026, 85 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 21 Sep 2026 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at under 1%. That’s in the top 40% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Linux has published a fix or advice.[3] CISA’s 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).”[1]

  1. Check whether you use it.Linux Kernel is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed (fixed by 8 commits to Linux, in the releases that include them), or not in use. CISA gave US government agencies until 21 Sep 2026 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at under 1%.[4]

See also

Other Linux Kernel flaws

Other out-of-bounds write flaws

  • CVE-2026-86950, Apple devices: out-of-bounds write ·
  • CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
  • CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·
  • CVE-2026-0300, Palo Alto Networks PAN-OS: out-of-bounds write ·
  • CVE-2026-3909, Google Skia: out-of-bounds write ·

Added the same day

  • CVE-2025-39964, Linux Kernel: race condition ·
  • CVE-2025-39682, Linux Kernel: improper check for unusual or exceptional conditions ·

Every Linux flaw on CISA’s list · Everything added in September 2026

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Linux Kernel Out-of-Bounds Write Vulnerability”. Known Exploited Vulnerabilities Catalog, added 18 Sep 2026.
  2. ^ National Institute of Standards and Technology. “CVE-2026-53266 Detail”. National Vulnerability Database, published 25 Jun 2026.
  3. ^ Linux. Advisories and fixes: git.kernel.org, git.kernel.org, git.kernel.org, git.kernel.org, git.kernel.org, and 3 more on NVD’s record.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.009, percentile 60.8, 31 Oct 2026.
  5. CVE Program. “CVE-2026-53266”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.