net: skbuff: don't touch shared zerocopy state in skb_tx_error() (CVE-2026-80977) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80977

net: skbuff: don't touch shared zerocopy state in skb_tx_error()

Answer in brief

CVE-2026-80977 records a Unknown severity vulnerability in net: skbuff: don't touch shared zerocopy state in skb_tx_error(). 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.

Published Sep 11, 2026Updated Sep 11, 2026Source checked Sep 11, 2026First seen by HOL Sep 11, 2026Material review Sep 11, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=25121173f7b1e4ac3fc692df6e7b8c52ec36abba <15aa81b390d401abf4b8211042470e9e92e3b7fb \|\| >=25121173f7b1e4ac3fc692df6e7b8c52ec36abba <288f9970670841044ab030104fa6b6ed159949d0 \|\| >=25121173f7b1e4ac3fc692df6e7b8c52ec36abba <0370da114a9bc044e248b85c6809d1b5e0c1f7f9 \|\| >=25121173f7b1e4ac3fc692df6e7b8c52ec36abba <f66bdb1cc0fcd227a062378f8be0b5873aa5600a	15aa81b390d401abf4b8211042470e9e92e3b7fb, 288f9970670841044ab030104fa6b6ed159949d0, 0370da114a9bc044e248b85c6809d1b5e0c1f7f9, f66bdb1cc0fcd227a062378f8be0b5873aa5600a
Linux/Linuxgeneric	3.8	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 15aa81b390d401abf4b8211042470e9e92e3b7fb if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 11, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: don't touch shared zerocopy state in skb_tx_error() skb_tx_error() completes the zerocopy uarg and clears SKBFL_ALL_ZEROCOPY, and skb_zcopy_downgrade_managed() clears SKBFL_MANAGED_FRAG_REFS. Both live in skb_shinfo(), which every clone shares, while the caller only owns the reference it is about to drop. Through a clone it tells the producer its pages are free and drops SKBFL_SHARED_FRAG for an skb that is still in flight. Open vSwitch reaches this with a non-last OVS_ACTION_ATTR_RECIRC: clone_execute() sends a skb_clone() into ovs_dp_process_packet() while do_execute_actions() keeps forwarding the original, and skb_clone() does not privatise the frags here -- skb_orphan_frags() returns early on SKBFL_DONT_ORPHAN. A flow miss on the clone then strips the marker from the packet still being forwarded, and a later local ESP delivery decrypts in place over frags it does not own privately. Skip it for a cloned skb. Nothing is lost: skb_release_data() clears the zerocopy state once the last reference to the shared data goes.

Quoted source text, attributed separately from HOL analysis.