FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2026-46300

Linux · Kernel · Linux Kernel Missing Initialization of a Variable Vulnerability

Verdict
Patch soon · actively exploited, not reachable unauthenticated from the internet, and in the top 5% of CVEs by near-term exploitation probability

Added to CISA KEV 2026-10-28 · exploited in the wild for 10 days

How a test catches it

Test
Submit the declared length boundary, one past it, and an order of magnitude past it, to every parameter that reaches a fixed or computed buffer, and watch for a crash, a reset, or a changed response length.
Passes when
The input is bounded before it reaches the buffer. A crash, a reset, or a silent change in response length under an oversized value is the finding, and confirming it needs no exploitation - the crash is the evidence.
What an attacker can reach How likely Time What CISA says to do Sources All 566

What an attacker can reach

CVSS 7.8 HIGH. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectorlocalrequires local access to the machine
Privileges requiredlowneeds some credentials, so a fully anonymous attacker cannot reach it directly
User interactionnonecan be triggered with nobody interacting with the page or request
Base vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
WeaknessCWE-787

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.1613, which places it in the top 5% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.1613
Percentile0.969 — top 5%

Time

Added to KEV2026-10-28
Days exploited10
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

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.

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.

Sources

This page describes the bug, not your estate. It cannot tell you whether you run it, or whether your own systems carry the same class of flaw. That question is what an assessment answers.

Web application penetration testing · API security testing · every service