Answer in brief
CVE-2026-53266 records a High severity (CVSS 8.8) vulnerability in netfilter: bridge: make ebt_snat ARP rewrite writable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53266 records a High severity (CVSS 8.8) vulnerability in netfilter: bridge: make ebt_snat ARP rewrite writable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=63137bc5882a1882c553d389fdeeeace86ee1741 <bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <76280b78cc9f23bdc6438e10ad6dff148ef8375b || >=63137bc5882a1882c553d389fdeeeace86ee1741 <b7e91939ba9be805a62a257fa4e227dffbb88fa0 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <afd64b59c3de9bbbdd3759e834fdc55cda716e0b || >=63137bc5882a1882c553d389fdeeeace86ee1741 <153ea96c806aea395daba907a4f88480b6ad5093 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <b18675263db1147c8e1cab625400c13a0d87bd2d || >=63137bc5882a1882c553d389fdeeeace86ee1741 <c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <67ba971ae02514d85818fe0c32549ab4bfa3bf49 || 2f3839075a5f8dcf116c1abe35b36b018ac62445 || 51ba2945a8ef65ae437c8f9ba05f0343aa82ae5b || b7d23c2c87584eb429f115c078ed511be8b18e29 || >=5.4.73 <5.5 || >=5.8.17 <5.9 || >=5.9.2 <5.10 | bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87, 76280b78cc9f23bdc6438e10ad6dff148ef8375b, b7e91939ba9be805a62a257fa4e227dffbb88fa0, afd64b59c3de9bbbdd3759e834fdc55cda716e0b, 153ea96c806aea395daba907a4f88480b6ad5093, b18675263db1147c8e1cab625400c13a0d87bd2d, c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5, 67ba971ae02514d85818fe0c32549ab4bfa3bf49, 5.5, 5.9, 5.10 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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().
Quoted source text, attributed separately from HOL analysis.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=63137bc5882a1882c553d389fdeeeace86ee1741 <bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <76280b78cc9f23bdc6438e10ad6dff148ef8375b || >=63137bc5882a1882c553d389fdeeeace86ee1741 <b7e91939ba9be805a62a257fa4e227dffbb88fa0 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <afd64b59c3de9bbbdd3759e834fdc55cda716e0b || >=63137bc5882a1882c553d389fdeeeace86ee1741 <153ea96c806aea395daba907a4f88480b6ad5093 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <b18675263db1147c8e1cab625400c13a0d87bd2d || >=63137bc5882a1882c553d389fdeeeace86ee1741 <c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5 || >=63137bc5882a1882c553d389fdeeeace86ee1741 <67ba971ae02514d85818fe0c32549ab4bfa3bf49 || 2f3839075a5f8dcf116c1abe35b36b018ac62445 || 51ba2945a8ef65ae437c8f9ba05f0343aa82ae5b || b7d23c2c87584eb429f115c078ed511be8b18e29 || >=5.4.73 <5.5 || >=5.8.17 <5.9 || >=5.9.2 <5.10 | bf84ad7c7a9ede46e31afaa41a1ba06a159e8c87, 76280b78cc9f23bdc6438e10ad6dff148ef8375b, b7e91939ba9be805a62a257fa4e227dffbb88fa0, afd64b59c3de9bbbdd3759e834fdc55cda716e0b, 153ea96c806aea395daba907a4f88480b6ad5093, b18675263db1147c8e1cab625400c13a0d87bd2d, c9b5ff59feffb92a147a84a5aa28acd2cb8ff4c5, 67ba971ae02514d85818fe0c32549ab4bfa3bf49, 5.5, 5.9, 5.10 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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().
Quoted source text, attributed separately from HOL analysis.