Stackurity Start free trial

CVEs / CVE-2026-53266

CVE-2026-53266: Linux Kernel Out-of-Bounds Write Vulnerability

Are you affected? Check your servers with Stackurity: it lists the software on each server and the vulnerabilities to fix first.

Check your servers with Stackurity Already using Stackurity? Search for CVE-2026-53266

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.

CISA, Known Exploited Vulnerabilities catalog

Description

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

The CVE record, via NVD · published 25 Jun 2026 · NVD status: Analyzed

Affected and fixed versions

As stated by the CVE record (from the CNA)
ProductAffectedFixed in
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before 76280b78cc9f23bdc6438e10ad6dff148ef8375b76280b78cc9f23bdc6438e10ad6dff148ef8375b
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before b7e91939ba9be805a62a257fa4e227dffbb88fa0b7e91939ba9be805a62a257fa4e227dffbb88fa0
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before afd64b59c3de9bbbdd3759e834fdc55cda716e0bafd64b59c3de9bbbdd3759e834fdc55cda716e0b
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before 153ea96c806aea395daba907a4f88480b6ad5093153ea96c806aea395daba907a4f88480b6ad5093
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before b18675263db1147c8e1cab625400c13a0d87bd2db18675263db1147c8e1cab625400c13a0d87bd2d
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5
Linux Linuxfrom 63137bc5882a1882c553d389fdeeeace86ee1741, before 67ba971ae02514d85818fe0c32549ab4bfa3bf4967ba971ae02514d85818fe0c32549ab4bfa3bf49
Linux Linux2f3839075a5f8dcf116c1abe35b36b018ac62445—
Linux Linux51ba2945a8ef65ae437c8f9ba05f0343aa82ae5b—
Linux Linuxb7d23c2c87584eb429f115c078ed511be8b18e29—
Linux Linuxfrom 5.4.73, before 5.55.5
Linux Linuxfrom 5.8.17, before 5.95.9
Linux Linuxfrom 5.9.2, before 5.105.10
Linux Linux5.10—
As stated by OSV
ProductAffectedFixed in
Kernel (Linux)from 5.10.0, before 5.10.2595.10.259
Kernel (Linux)from 5.11.0, before 5.15.2105.15.210
Kernel (Linux)from 5.16.0, before 6.1.1766.1.176
Kernel (Linux)from 6.2.0, before 6.6.1436.6.143
Kernel (Linux)from 6.7.0, before 6.12.946.12.94
Kernel (Linux)from 6.13.0, before 6.18.366.18.36
Kernel (Linux)from 6.19.0, before 7.0.137.0.13

Exploitation

In CISA KEV since18 Sep 2026
Due date for US federal agencies21 Sep 2026
Used in ransomware campaignsUnknown
Required actionApply 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.

Severity

CVSS 3.18.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Scored by the CNA (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
WeaknessCWE-787

References

Sources

Exploitation status from the CISA Known Exploited Vulnerabilities catalog. EPSS scores from FIRST. Descriptions, severity and references from the National Vulnerability Database. Open-source package versions from OSV (CC-BY 4.0). Text is shown as each source states it; Stackurity does not edit it. Check the vendor's advisory before acting.

This product uses data from the NVD API but is not endorsed or certified by the NVD.