Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-46300

high CISA KEV

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach…

Vendor / product: Linux — linux kernel

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.

CVSS
7.8
7.8 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-05-23 12:17
Modified: 2026-10-29 04:18
NVD status: Undergoing Analysis
Last synced 1 hour ago
Verified against the source API 2026-10-29 04:43 UTC
Exploitation
Listed in CISA KEV
Added 2026-10-28 · due 2026-10-31
Known ransomware use: not reported

Required action (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.

Affected products

linux / linux_kernel ≥3.9 ≤5.10.257, ≥5.11 <5.15.208, ≥5.16 <6.1.174, ≥6.2 <6.6.141, ≥6.7 <6.12.91, ≥6.13 <6.18.33

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/2f2b16022a2e10ca7bccfb98db5ed2ec0f72641c
Patch / mitigation: https://git.kernel.org/stable/c/3599e6b3cc1ada96883d496a50a210d3afbb6987
Patch / mitigation: https://git.kernel.org/stable/c/3884358a9286b17f389a72b1426fc4547c23c111
Patch / mitigation: https://git.kernel.org/stable/c/3bd9e113d50034db99d7ef69fd8e5242d15e414a
Patch / mitigation: https://git.kernel.org/stable/c/760e1addc27ba1a7beb4a0a7e8b3e9ec49e7a34e
Patch / mitigation: https://git.kernel.org/stable/c/78bf6b6bb19541d19fbda6242e7cfe2c682763c0
Patch / mitigation: https://git.kernel.org/stable/c/9d3e5fd19fe1063bf607219e8562fbd567b8e8d5
Patch / mitigation: https://git.kernel.org/stable/c/f84eca5817390257cef78013d0112481c503b4a3

References

Data sources

NVD CVE API 2.0 — fetched 2026-10-29 04:43 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs