Skip to content
Reachability Analysis

CVE-2026-53266: Linux kernel, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

ebtables is the Linux tool for filtering and rewriting Ethernet frames on a bridge. Its snat target changes the source MAC address. With the --snat-arp option it also rewrites the sender hardware address inside ARP packets.

The ARP rewrite used skb_store_bits() to write directly into the packet buffer, but it never made that range writable first. If the range sat in a nonlinear buffer fragment that is backed by a file page imported through splice, the kernel wrote the new MAC address straight into the page cache copy of that file. The fix calls skb_ensure_writable() on the ARP range before the header is read and before the write.

CISA describes the result as an out-of-bounds write into a file-backed page. Red Hat says a local attacker can reach privilege escalation, memory corruption or denial of service, and that the impact is limited to hosts with the special bridge netfilter rules. The bytes written are a MAC address.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
Version: the kernel is in an affected range and carries no fix or distribution backport.Run uname -r and compare with the versions table. On RPM systems run rpm -q --changelog kernel | grep CVE-2026-53266. On Debian and Ubuntu run apt changelog linux-image-$(uname -r) | grep CVE-2026-53266, or use the Debian and Ubuntu trackers.
An ebtables nat rule uses the snat target with ARP rewrite, so the ebtable_nat and ebt_snat modules are loaded.Run ebtables -t nat -L as root and look for -j snat rules that include --snat-arp (the ebtables manual describes this option as changing the hardware source address inside ARP messages). Also check rule files that load at boot, for example /etc/sysconfig/ebtables or your firewall tooling. Then run lsmod | grep -E 'ebtable_nat|ebt_snat'. If neither module is loaded and no ebtables nat rule exists, the vulnerable code does not run, but loading state changes when a rule is added.
A bridge in the same network namespace carries the ARP traffic.Run ip link show type bridge and bridge link. Repeat inside container and VM host network namespaces that run their own bridges, for example with ip netns exec <name> ebtables -t nat -L.
An attacker can run code locally as a low-privilege user and can reach CAP_NET_ADMIN over the namespace that holds the rule.Run sysctl user.max_user_namespaces (0 means no new user namespaces) and list local accounts that can run code. The kernel source requires CAP_NET_ADMIN in the owning user namespace to change ebtables rules.
The kernel line still gets fixes.Kernel 5.4 ended with 5.4.302 on 3 Dec 2025 and has no fix. On such hosts only a move to a supported kernel or the Red Hat mitigation removes the exposure.

Affected and fixed versions

NVD's lower bounds (5.4.73, 5.8.17, 5.9.2) are the stable releases that first picked up commit 63137bc5882a, which the fix cites as its origin. Releases before those do not carry the bug. Red Hat kpatch errata of 28 Oct 2026 exist for RHEL 8 (RHSA-2026:92062), RHEL 9 (RHSA-2026:91650) and RHEL 10 (RHSA-2026:92061).
Product or lineAffectedFirst fixed
Linux 5.45.4.73 to 5.4.302 (last release)No fix; the line is end-of-life
Linux 5.85.8.17 and later 5.8 releasesNo stable fix; the line is end-of-life
Linux 5.9 and 5.105.9.2 and later 5.9 releases, and 5.10.0 to before 5.10.2595.10.259 (19 Jun 2026). The 5.9 line is end-of-life with no fix
Linux 5.155.11 to before 5.15.2105.15.210 (19 Jun 2026)
Linux 6.15.16 to before 6.1.1766.1.176 (19 Jun 2026)
Linux 6.66.2 to before 6.6.1436.6.143 (19 Jun 2026)
Linux 6.126.7 to before 6.12.946.12.94 (19 Jun 2026)
Linux 6.186.13 to before 6.18.366.18.36 (19 Jun 2026)
Linux 7.06.19 to before 7.0.137.0.13 (19 Jun 2026)
Linux 7.17.1-rc1 to 7.1-rc67.1 (14 Jun 2026), mainline commit 67ba971ae025 in 7.1-rc7
RHEL 10 / 10.0 EUS / NVIDIA for RHEL 10All earlier kernelskernel-6.12.0-211.59.1.el10_2 (RHSA-2026:71233, 24 Sep 2026) / kernel-6.12.0-55.106.1.el10_0 (RHSA-2026:71326) / kernel-6.12.0-231.20.el10nv (RHSA-2026:72059)
RHEL 9 / 9.6 EUS / 9.4 / 9.2 extendedAll earlier kernelskernel-5.14.0-687.23.1.el9_8 (RHSA-2026:36645, 8 Jul 2026) / 5.14.0-570.143.1.el9_6 (RHSA-2026:71327) / 5.14.0-427.152.1.el9_4 (RHSA-2026:71569) / 5.14.0-284.194.1.el9_2 (RHSA-2026:71601)
RHEL 8 and extended streamsAll earlier kernelskernel-4.18.0-553.143.1.el8_10 (RHSA-2026:39083, 14 Jul 2026) / 4.18.0-477.169.1.el8_8 (RHSA-2026:71325) / 4.18.0-372.217.1.el8_6 (RHSA-2026:70797) / 4.18.0-305.209.1.el8_4 (RHSA-2026:71565)
RHEL 7 ELS / RHEL 6 ELSAll earlier kernelskernel-3.10.0-1160.164.1.el7 (RHSA-2026:71687, 24 Sep 2026) / kernel-2.6.32-754.64.1.el6 (RHSA-2026:73732, 30 Sep 2026)
DebianEarlier source packagesbullseye 5.10.259-1 (DLA-4664-1), bookworm 6.1.176-1 (DLA-4665-1), trixie 6.12.94-1, unstable 7.0.13-1; linux-6.1 on bullseye 6.1.176-1~deb11u1 (DLA-4671-1)
Ubuntu linux packageEarlier kernelsjammy 5.15.0-198.208, noble 6.8.0-146.146, resolute 7.0.0-31.31, jammy HWE 6.8.0-149.149~22.04.1. Focal has no fix yet (needed); questing is end-of-life. Trusty, xenial and bionic are not affected

If the fix cannot go in yet

  • Install a kernel with the fix and reboot. Cost: a reboot. Red Hat also ships kpatch updates for some streams.
  • Red Hat mitigation: disable ARP hardware address rewriting in ebtables SNAT rules, or remove ebtables SNAT rules that act on ARP traffic on bridge interfaces. Cost: the bridge no longer rewrites the ARP sender address, so any set-up that depends on that rewrite (for example MAC address translation for bridged virtual machines or containers) stops working.
  • CISA's KEV description warns the product could be end-of-life and advises moving to a supported version. Cost: a kernel upgrade project.
  • Optional hardening beyond the vendor text: unload ebtable_nat and ebt_snat if no rule needs them. Cost: all ebtables nat rules stop working.

What to look for

  • CISA's KEV entry marks forensic triage as required and gives no indicators. Red Hat, Debian, Ubuntu and the kernel project publish no log strings, file paths or addresses for this CVE.
  • The write goes to a cached file page, so a checksum of the file on disk does not show it. Review local accounts that could create network namespaces and ebtables rules on hosts that run bridges.

The earliest dated mark of exploitation is CISA's, on 18 Sep 2026, 109 days after disclosure; exploitation may have begun earlier.

Exploitation reported so far

CISA added the flaw to KEV on 18 Sep 2026 and lists ransomware use as unknown. The KEV entry gives no details of the attacks. The CISA entry in the NVD record carries an SSVC decision of exploitation active, automatable no and technical impact total, stamped 18 Sep 2026.

Neither CISA, Red Hat, Debian, Ubuntu nor the kernel project names the actor or the targets, and no researcher has published a description of the attacks.

Why runtime reachability settles it

The flaw only runs when an ebtables nat rule with ARP rewrite exists on a bridge and a local user can reach it. The kernel version alone cannot show that, but reading the loaded modules and the ebtables rules on the running host can: that is runtime state, not source code. Known-exploited status says to act, and the rule check says where. See runtime reachability for what the method proves and misses.

Sources

  1. CVE-2026-53266: NVD record, read 19 Nov 2026
  2. CVE-2026-53266: CISA KEV feed (catalog version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-53266: vendor advisory data (Red Hat Security Data API: errata, package versions, mitigation, statement), read 19 Nov 2026
  4. CVE-2026-53266: upstream fix commit (GitHub mirror of the Linux kernel); the seven stable commits in the KEV notes were read the same way, read 19 Nov 2026
  5. CVE-2026-53266: upstream commit named as the origin of the bug, read 19 Nov 2026
  6. CVE-2026-53266: kernel.org stable change log 6.1.176 (also read for 5.10.259, 5.15.210, 6.6.143, 6.12.94, 6.18.36, 7.0.13, 7.1, 5.4.73, 5.8.17, 5.9.2 and 5.4.300 to 5.4.302), read 19 Nov 2026
  7. CVE-2026-53266: Linux 6.12 kernel source, ebtables.c (capability check for rule changes), read 19 Nov 2026
  8. CVE-2026-53266: Linux 6.12 kernel source, ebt_snat.c (code before the fix), read 19 Nov 2026
  9. CVE-2026-53266: ebtables manual page (snat target and --snat-arp option), read 19 Nov 2026
  10. CVE-2026-53266: Debian security tracker, read 19 Nov 2026
  11. CVE-2026-53266: Ubuntu CVE tracker data, read 19 Nov 2026
  12. CVE-2026-53266: GitHub advisory database entry GHSA-xmhg-rr34-2chj, read 19 Nov 2026

Last reviewed 19 Nov 2026.