CVE-2026-46300: high-severity vulnerability in Linux
net: skbuff: preserve shared-frag marker during coalescing
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
Patch now. It under exploitation confirmed by CISA, has an official Brazilian government alert and has a working public exploit.
Brazil's federal government published an alert, recommendation or bulletin that cites this vulnerability.
- CTIR Gov · ALERTA 103/2026 · 29 Oct 2026Vulnerabilidade crítica no Kernel - Linuxread on gov.br ↗
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
A flaw in the Linux kernel's network buffer handling can lose a marker that warns other code that some data is shared. This can cause the kernel to modify data it should have copied first, which may corrupt data that other parts of the system rely on.
In skb_try_coalesce(), paged fragments transferred from a source skb with SKBFL_SHARED_FRAG set are attached to the destination skb without propagating that flag. ESP input relies on skb_has_shared_frag() to skip skb_cow_data() for uncloned nonlinear skbs, so after TCP receive coalescing it can perform in-place decryption over page-cache-backed frags. The reported impact is unintended in-place writes to shared, externally owned memory, affecting integrity; the fix in the Linux kernel propagates the marker during frag transfer.
In the same product, most dangerous first.