~/exploited / cve-2026-53266
CVE-2026-53266: Linux Kernel
According to CISA this vulnerability is already used in attacks (added on 18 September 2026).
Key facts
| CVE | CVE-2026-53266 |
|---|---|
| Vendor | Linux — Kernel |
| Vulnerability | Linux Kernel Out-of-Bounds Write Vulnerability |
| Added | 18 September 2026 |
| Deadline (US agencies) | 21 September 2026 |
| Ransomware campaigns | unknown |
Technical data (NVD, FIRST EPSS)
| CVSS base score | 8.8 (high) · CVSS 3.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HAttack local, complexity: low, privileges: low needed, user interaction: none |
|---|---|
| EPSS (exploitation probability) | Probability of exploitation in the next 30 days: 0.93%. Higher than 61.5% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks. |
| Weakness type (CWE) | CWE-787 — Out-of-bounds Write |
| Affected versions | linux kernel: >= 5.4.73, < 5.5 linux kernel: >= 5.8.17, < 5.9 linux kernel: >= 5.9.2, < 5.10.259 linux kernel: >= 5.11, < 5.15.210 linux kernel: >= 5.16, < 6.1.176 linux kernel: >= 6.2, < 6.6.143 linux kernel: >= 6.7, < 6.12.94 linux kernel: >= 6.13, < 6.18.36 and 2 more |
Description (NVD)
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().
Patches and vendor advisories
- git.kernel.org/stable/c/153ea96c806aea395daba907a4f88480b6ad5093
- git.kernel.org/stable/c/67ba971ae02514d85818fe0c32549ab4bfa3bf49
- git.kernel.org/stable/c/76280b78cc9f23bdc6438e10ad6dff148ef8375b
- git.kernel.org/stable/c/afd64b59c3de9bbbdd3759e834fdc55cda716e0b
- git.kernel.org/stable/c/b18675263db1147c8e1cab625400c13a0d87bd2d
Description (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.
Required action (CISA)
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.
What admins should do now
- Affected? Check whether Linux Kernel is in use and which version runs (package manager, admin UI,
--version). - Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
- Review logs back to 18 September 2026: unusual logins, new files, unexpected processes, outbound connections.
- If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.
The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.
Sources
- CISA KEV Catalog
- NVD CVE-2026-53266
- git.kernel.org/stable/c/bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87
- git.kernel.org/stable/c/76280b78cc9f23bdc6438e10ad6dff148ef8375b
- git.kernel.org/stable/c/b7e91939ba9be805a62a257fa4e227dffbb88fa0
- git.kernel.org/stable/c/afd64b59c3de9bbbdd3759e834fdc55cda716e0b
- git.kernel.org/stable/c/153ea96c806aea395daba907a4f88480b6ad5093
- git.kernel.org/stable/c/b18675263db1147c8e1cab625400c13a0d87bd2d
New articles by e-mail
One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).