Home › Vulnerabilities

Linux Kernel: Exploited Flaw CVE-2026-46300

Published October 29, 2026 · Last updated October 29, 2026

Linux Linux Kernel CVE KEV Patch

What happened: On October 28, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-46300, a flaw in Linux Kernel, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "Linux Kernel Missing Initialization of a Variable Vulnerability."

CISA's summary: "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."

What the National Vulnerability Database says

NVD first published CVE-2026-46300 on May 23, 2026. Its description, from the record's source (416baaa9-dc9f-4396-8d5f-8c081fb06d67), reads: "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."

How serious is CVE-2026-46300?

The CVSS 3.1 base score is 7.8 out of 10 (High), scored by nist.gov. In plain terms: an attacker can reach the Kernel weakness only with local access to the system; the attacker needs a low-privilege account; no one has to click or open anything. The listed impact on Kernel data secrecy is high, on data integrity high, and on availability high. The full vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Which Kernel versions are affected?

The CVE record lists these affected ranges:

  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 3599e6b3cc1ada96883d496a50a210d3afbb6987
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 2f2b16022a2e10ca7bccfb98db5ed2ec0f72641c
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 9d3e5fd19fe1063bf607219e8562fbd567b8e8d5
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 78bf6b6bb19541d19fbda6242e7cfe2c682763c0
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 760e1addc27ba1a7beb4a0a7e8b3e9ec49e7a34e
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 3bd9e113d50034db99d7ef69fd8e5242d15e414a
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, 3884358a9286b17f389a72b1426fc4547c23c111
  • cef401de7be8c4e155c6746bfccf721a4fa5fab9 up to, but not including, f84eca5817390257cef78013d0112481c503b4a3

If your Kernel version falls in one of these ranges, check Linux's advisory for the fixed release that applies to you.

What kind of weakness is it?

CISA and NVD map CVE-2026-46300 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):

  • CWE-456: Missing Initialization of a Variable. MITRE's definition: "The product does not initialize critical variables, which causes the execution environment to use unexpected values."

CISA required action for CVE-2026-46300

CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "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."

Timeline for CVE-2026-46300

  • May 23, 2026: NVD publishes CVE-2026-46300.
  • October 28, 2026: CISA adds CVE-2026-46300 to the KEV catalog.
  • October 29, 2026: latest change to the NVD record (status: Undergoing Analysis).
  • October 31, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-46300.

Other scores in the NVD record: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 scores it 7.8 (High) under CVSS 3.1; 0b0ca135-0b70-47e7-9f44-1890c2a1c46c scores it 7.8 (High) under CVSS 3.1.

Advisories and technical references

The NVD record for CVE-2026-46300 links to these references; tags in brackets are NVD's labels:

What to do

  • Run Linux Kernel? Follow Linux's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
  • Federal civilian agencies must act by October 31, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for Kernel too.
  • Ransomware use: CISA lists known ransomware campaign use for CVE-2026-46300 as "Unknown".
  • Don't run Kernel yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-46300" and asks for payment or remote access, that is a scam pattern, not a Linux alert.

CVE-2026-46300 record details from CISA and NVD

  • CISA forensic triage flag for CVE-2026-46300: Yes
  • Attack complexity for CVE-2026-46300: low
  • CVE-2026-46300 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-46300: exploitability 1.8, impact 5.9.
  • Who mapped the weakness type: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c (Secondary); 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary); [email removed] (Primary)
  • NVD product identifiers (CPE): cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*, cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
  • References in the NVD record: 51 (8 tagged Patch, 4 tagged Mailing List).
  • CISA SSVC decision points for CVE-2026-46300 (from NVD): exploitation=active; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.