PatchSiren cyber security CVE debrief
CVE-2026-80977 Linux CVE debrief
A vulnerability in the Linux kernel's network stack has been addressed. The issue, resolved in a recent commit, pertains to the handling of zerocopy state in the `skb_tx_error()` function. When a cloned skb is passed to this function, it could potentially modify shared zerocopy state, leading to unexpected behavior. This situation can occur in Open vSwitch when a non-last `OVS_ACTION_ATTR_RECIRC` action is executed, causing a cloned skb to be sent into `ovs_dp_process_packet()` while the original skb continues to be forwarded. To address this, the code now skips modifying the zerocopy state for cloned skbs, ensuring that the state remains consistent and accurate.
- Vendor
- Linux
- Product
- Linux kernel
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Linux kernel maintainers, Linux distribution maintainers, Open vSwitch users, and administrators of systems utilizing the Linux kernel should assess their exposure to this vulnerability and verify the presence of the fix.
Why it matters
CVE-2026-80977 is a Linux kernel vulnerability that requires verification of exposure and fix presence, particularly in Open vSwitch environments.
- Verification of Linux kernel versions and Open vSwitch configurations is necessary to ensure the fix is applied
- Potential inconsistencies in zerocopy state handling could lead to unexpected behavior or crashes
- Administrators should monitor for issues related to zerocopy state handling in the Linux kernel
Technical summary
The Linux kernel vulnerability (CVE-2026-80977) relates to the handling of zerocopy state in the `skb_tx_error()` function. When a cloned skb is passed to this function, it could potentially modify shared zerocopy state. The issue arises in Open vSwitch when a non-last `OVS_ACTION_ATTR_RECIRC` action is executed. The code now skips modifying the zerocopy state for cloned skbs to ensure consistency and accuracy.
Defensive priority
Linux kernel maintainers and users should assess exposure and verify the presence of the fix, particularly in environments utilizing Open vSwitch.
Recommended defensive actions
- Review Linux kernel configurations and versions to ensure the fix is applied
- Assess Open vSwitch usage and verify that updates have been applied
- Monitor for potential issues related to zerocopy state handling in the Linux kernel
- Perform a thorough review of system logs to detect any anomalies related to the Linux kernel
- Verify the integrity of the Linux kernel's network stack implementation
- Update documentation to reflect changes in zerocopy state handling for cloned skbs
- Conduct a risk assessment to identify potential vectors of exploitation in the environment
Evidence notes
The CVE record and associated source references provide details on the vulnerability and its resolution. However, the impact and affected versions require further verification from official sources. Linux kernel maintainers and users should assess exposure and verify the presence of the fix, particularly in environments utilizing Open vSwitch. The fix involves skipping modification of zerocopy state for cloned skbs to ensure consistency and accuracy. This change prevents potential inconsistencies that could lead to unexpected behavior
Sources and references
Verified primary and authoritative sources
-
CVE-2026-80977 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-80977
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-80977 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80977
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/0370da114a9bc044e248b85c6809d1b5e0c1f7f9
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/15aa81b390d401abf4b8211042470e9e92e3b7fb
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/288f9970670841044ab030104fa6b6ed159949d0
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f66bdb1cc0fcd227a062378f8be0b5873aa5600a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.