CVE-2026-80977

CVE CVE-2026-80977EUVD EUVD-2026-76300Published 2026-09-11T19:42:38.000ZLast changed 2026-09-14T11:59:22.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 5.15.221; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <288f9970670841044ab030104fa6b6ed159949d0; patch: 6.1.188; patch: 6.12.109; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <b4452349dcf4d561e13be768d5d278de58248930; patch: 0; patch: 7.3-rc1; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <6493165034bca14033bf49c9cec7b45e97a91497; patch: 7.2.4; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <6ec22afc82a3cae07ade0a6ec361ae2532128ff5; patch: 5.10.270; 3.8; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <15aa81b390d401abf4b8211042470e9e92e3b7fb; patch: 6.6.157; patch: 6.18.50; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <f66bdb1cc0fcd227a062378f8be0b5873aa5600a; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <0370da114a9bc044e248b85c6809d1b5e0c1f7f9; 25121173f7b1e4ac3fc692df6e7b8c52ec36abba <363c4252ffc473a0203e91b83ede5519dfb8bd07

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.