← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-46300 exploited? Yes: in CISA KEV since 28 Oct 2026

Gociux · Linux Kernel · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-46300, Linux Kernel Missing Initialization of a Variable Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 28 Oct 2026, 158 days after it was published. It affects Linux Kernel. If you run it, CISA's required action 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.

exploitedYesCISA KEV · 28 Oct 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity7.8CVSS 3.1 · high
US federal due31 Oct 2026BOD 22-01 deadline

What it is

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.

VendorLinux (32 exploited CVEs in KEV)
ProductKernel
VulnerabilityLinux Kernel Missing Initialization of a Variable Vulnerability
WeaknessCWE-456
Published23 May 2026
Added to KEV28 Oct 2026
Reported by (CNA)Linux

What to do

  1. Check whether you run it. Look for Kernel in your asset inventory, including appliances and cloud images. Stack check lists every exploited Linux CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 23 May 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Linux.

Other exploited CVEs in Kernel

References

Questions

Is CVE-2026-46300 being exploited?

Yes. CISA added CVE-2026-46300 to the Known Exploited Vulnerabilities catalog on 28 Oct 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-46300 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-46300?

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. Check Linux's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Kernel and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in October 2026 · Linux scorecard · act-now radar.

Running Linux in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →