Quick answer
Yes. CVE-2026-53266 in Linux Kernel is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on September 18, 2026. If you run Kernel, apply the vendor's fix now and check for signs of compromise.
What is CVE-2026-53266?
Linux Kernel Out-of-Bounds Write Vulnerability. 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.
Description from the CISA Known Exploited Vulnerabilities catalogue.
What kind of flaw is it?
A memory-safety bug that writes past the end of a buffer, commonly exploited to take control of the process.
Other exploited out-of-bounds writeWhy it matters
Flaws in operating systems, browsers and office software are exploited through malicious websites, documents and messages. They are often chained to give attackers code execution or higher privilege on staff devices.
Higher than 61% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Check that automatic updates are enabled and devices are on the fixed version. | 1Push the update to all affected devices and restart where required. |
2Use your device management or vulnerability scanning tools to find machines that have not updated. | 2Remove devices that cannot be updated from sensitive networks. |
3Prioritize devices used by administrators, executives and finance staff. | 3Track patch coverage as an ongoing measure, not a one-off check. |
Am I affected? How to check
- 1Check that automatic updates are enabled and devices are on the fixed version.
- 2Use your device management or vulnerability scanning tools to find machines that have not updated.
- 3Prioritize devices used by administrators, executives and finance staff.
What to do now
- 1Push the update to all affected devices and restart where required.
- 2Remove devices that cannot be updated from sensitive networks.
- 3Track patch coverage as an ongoing measure, not a one-off check.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
Deadline and priority
CISA requires US federal civilian agencies to remediate catalogued vulnerabilities by the listed due date under Binding Operational Directive 22-01 (September 21, 2026 for this one), and strongly urges every organization to prioritize them the same way.
In the news
- Flipper Devices launches $399 ‘Flipper One’ Linux-based multi-toolBleepingComputer · November 17, 2026
- SANSAR Linux Cryptomining Malware Uses Modified NVIDIA Library to Hide GPU ActivityThe Hacker News · November 16, 2026
- ThreatsDay: 59 Linux Kernel Bugs, Falcon Spyware, GSocket Backdoors + 17 More StoriesThe Hacker News · November 12, 2026
- Lessons from 59 Linux Kernel Bug ReportsMicrosoft Security Blog · November 11, 2026
- Get root on a musl Linux system by slamming it with an overly long passwordThe Register · November 5, 2026
More in the daily briefing.
Common questions
Is CVE-2026-53266 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on September 18, 2026.
How do I fix CVE-2026-53266?
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Check the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my Linux Kernel affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.
Sources
- 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
- nvd.nist.gov/vuln/detail/CVE-2026-53266
- CISA Known Exploited Vulnerabilities catalogue