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()… (CVE-2026-80977)
A vulnerability in the Linux kernel's network stack involving improper handling of shared zerocopy state in skb_tx_error() has been resolved. The flaw occurs because skb_tx_error() and skb_zcopy_downgrade_managed() modify shared state in skb_shinfo() that is cloned and shared among multiple references, leading to incorrect signaling that pages are free while still in use. This can cause issues such as local ESP packet decryption operating on fragments it does not exclusively own. The fix involves skipping this handling for cloned skbs to avoid premature clearing of zerocopy state.
AI Analysis
Technical Summary
The Linux kernel vulnerability (CVE-2026-80977) arises from skb_tx_error() improperly modifying shared zerocopy state flags in skb_shinfo(), which is shared among skb clones. This results in signaling that pages are free and dropping SKBFL_SHARED_FRAG for skbs still in flight, potentially causing data corruption or incorrect processing in subsystems like Open vSwitch and ESP packet handling. The issue is triggered when a cloned skb is processed without privatizing fragments, leading to a flow miss that strips markers from the original packet still being forwarded. The resolution is to skip zerocopy state handling for cloned skbs, ensuring skb_release_data() clears the state only when the last reference is dropped.
Potential Impact
This vulnerability can lead to incorrect handling of network packet fragments, potentially causing data corruption or improper packet processing in kernel networking components such as Open vSwitch and ESP decryption. There is no indication of remote code execution or privilege escalation. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to skip zerocopy state modifications for cloned skbs, preventing premature clearing of shared state. Users should apply the official kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to the patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; users should consult the vendor or kernel mailing list advisories for the exact fixed versions.
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()… (CVE-2026-80977)
Description
A vulnerability in the Linux kernel's network stack involving improper handling of shared zerocopy state in skb_tx_error() has been resolved. The flaw occurs because skb_tx_error() and skb_zcopy_downgrade_managed() modify shared state in skb_shinfo() that is cloned and shared among multiple references, leading to incorrect signaling that pages are free while still in use. This can cause issues such as local ESP packet decryption operating on fragments it does not exclusively own. The fix involves skipping this handling for cloned skbs to avoid premature clearing of zerocopy state.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability (CVE-2026-80977) arises from skb_tx_error() improperly modifying shared zerocopy state flags in skb_shinfo(), which is shared among skb clones. This results in signaling that pages are free and dropping SKBFL_SHARED_FRAG for skbs still in flight, potentially causing data corruption or incorrect processing in subsystems like Open vSwitch and ESP packet handling. The issue is triggered when a cloned skb is processed without privatizing fragments, leading to a flow miss that strips markers from the original packet still being forwarded. The resolution is to skip zerocopy state handling for cloned skbs, ensuring skb_release_data() clears the state only when the last reference is dropped.
Potential Impact
This vulnerability can lead to incorrect handling of network packet fragments, potentially causing data corruption or improper packet processing in kernel networking components such as Open vSwitch and ESP decryption. There is no indication of remote code execution or privilege escalation. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to skip zerocopy state modifications for cloned skbs, preventing premature clearing of shared state. Users should apply the official kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to the patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; users should consult the vendor or kernel mailing list advisories for the exact fixed versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-ppq5-hh8r-qqhh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-80977"]
Threat ID: 6aa4a02c55bf5e2cf5a86b59
Added to database: 09/12/2026, 00:43:24 UTC
Last enriched: 09/12/2026, 01:23:31 UTC
Last updated: 09/12/2026, 03:01:26 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.