CVE Alert: CVE-2026-53266 – Linux

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

This is a priority-1 kernel vulnerability because exploitation is reported as active and successful compromise could have total impact.

The flaw provides a memory-corruption primitive capable of undermining isolation, altering file-backed data, and potentially enabling privilege escalation or code execution. It is particularly concerning on shared infrastructure, where a compromised workload could target the host or neighbouring tenants. Exploitation is not broadly remote, but the impact justifies urgent action wherever the relevant networking functionality is enabled.

### Most likely attack path

An attacker first obtains limited local control with network-administration capability, then creates a bridge/ebtables rule and sends crafted ARP traffic through the bridge. Local access and deliberate shared, non-linear packet memory are required; no user interaction or timing race is needed. Scope crossing means a successful attack may escape a network namespace or container boundary and affect the host.

### Who is most exposed

Prioritise container hosts, virtualisation platforms, network appliances, routers, firewalls, and systems using Linux bridges with ebtables or equivalent legacy netfilter configuration. Risk is lower on systems without bridge netfilter functionality or without untrusted users able to create network namespaces.

Alert on unexpected `CAP_NET_ADMIN`, user-namespace, bridge, or ebtables activity.

Review new bridge interfaces, forwarding rules, and SNAT rules.

Correlate crafted or anomalous ARP traffic with namespace creation.

Monitor kernel warnings, crashes, unexplained file changes, and integrity failures.

### Mitigation and prioritisation

Treat as priority 1; deploy the vendor kernel update through an accelerated change.

Restrict untrusted user and network-namespace creation.

Disable bridge netfilter/ebtables where operationally unnecessary.

Apply kernel lockdown, integrity monitoring, and host isolation as compensating controls.

Reboot or otherwise verify the running kernel after patching; confirm in-use images, hypervisors, and appliances are covered.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.