Exploited vulnerabilities · Linux
CVE-2026-46300
Linux Kernel Missing Initialization of a Variable Vulnerability
Linux Kernel contains a missing initialization of a variable vulnerability that could allow for unintended modification of page-cache-backed data via failure to preserve the shared-fragment marker during socket buffer coalescing, causing ESP input processing to decrypt shared fragments in place. This vulnerability can be chained with CVE-2026-109618 and CVE-2026-109619 to implant PHP webshells and run commands as root.
Description in the NVD
In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost. That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skb_has_shared_frag() before deciding whether an uncloned nonlinear skb can skip skb_cow_data(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skb_has_shared_frag() as false and decrypt in place over page-cache backed frags. Propagate SKBFL_SHARED_FRAG when skb_try_coalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to's linear data rather than transferring frag descriptors.
Required action according to CISA
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.
What to do now
- Check your exposureFind out whether Linux Kernel runs anywhere in your environment, including systems of suppliers.
- Patch or mitigateApply the vendor update. If that is not possible at once, use the vendor's mitigation or take the system off the network.
- Look for signs of an attackThis vulnerability is exploited in real attacks. Review the logs of affected systems for the time before the patch.
References
- git.kernel.org/stable/c/2f2b16022a2e10ca7bccfb98db5ed2ec0f72641c
- git.kernel.org/stable/c/3599e6b3cc1ada96883d496a50a210d3afbb6987
- git.kernel.org/stable/c/3884358a9286b17f389a72b1426fc4547c23c111
- git.kernel.org/stable/c/3bd9e113d50034db99d7ef69fd8e5242d15e414a
- git.kernel.org/stable/c/760e1addc27ba1a7beb4a0a7e8b3e9ec49e7a34e
- git.kernel.org/stable/c/78bf6b6bb19541d19fbda6242e7cfe2c682763c0
- git.kernel.org/stable/c/9d3e5fd19fe1063bf607219e8562fbd567b8e8d5
- git.kernel.org/stable/c/f84eca5817390257cef78013d0112481c503b4a3
- nvd.nist.gov/vuln/detail/CVE-2026-46300
More exploited vulnerabilities in Linux products
Data: CISA Known Exploited Vulnerabilities Catalog and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.