Skip to main content

Linux Kernel CVE-2026-99077

| EUVDEUVD-2026-108743 HIGH
2026-10-23 Linux GHSA-xqqf-wrfv-j8jm
7.4
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify victim with connected UDP socket
  2. Delivery
    Send ICMP Frag-Needed/Redirect quoting guessed UDP port
  3. Exploit
    FNHE created before socket match
  4. Execution
    Probe FNHE cache for observable change
  5. Impact
    Infer ephemeral source port for off-path spoofing

Vulnerability Assessment

Exploitation Conditions

Exploitation requires a victim host running a pre-patch Linux kernel that has a connected (or wildcard) UDP socket whose ephemeral port the attacker wants to discover, and an off-path attacker able to deliver ICMP Fragmentation-Needed or Redirect messages that the host locally processes. The limiting factors are substantial: it is a probabilistic side-channel (CVSS AC:H) requiring repeated guesses and observation of the FNHE cache rather than a single deterministic request, and it yields only the ephemeral port number - useful mainly as a precursor to off-path injection attacks, not direct host compromise. The description notes prior randomization/hashing mitigations exist but were bypassable, which is why the condition holds across hardened kernels until this fix is applied.

Impact

Signals are mixed and point to a moderate, patch-in-due-course priority rather than an emergency. The input CVSS of 7.4 (High) is driven by C:H/I:H, but that impact rating looks overstated against the described mechanism: the flaw is an off-path side-channel that lets an attacker infer the ephemeral port of a connected UDP socket by forcing FIB nexthop exceptions (FNHE) to be created before socket matching. That is fundamentally an information-disclosure/port-derandomization weakness whose primary value is enabling follow-on off-path injection (e.g. UDP/DNS spoofing), not direct high-confidentiality or high-integrity compromise of the host - verify the C:H/I:H weighting with the kernel CNA. The exploitation-difficulty signals agree with low real-world urgency: AC:H reflects the probing/collision work needed, EPSS is 0.21% (11th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis (the only references are the two stable patch commits and the NVD entry). The decision label is this_week, consistent with a High-severity but non-emergency kernel fix. The main amplifier is prevalence: Linux is ubiquitous, so even a niche side-channel has broad aggregate exposure and should be rolled out through normal kernel patch cycles. Note the description explicitly states prior mitigations (siphash hashing, randomized bucket occupancy) were bypassable, which is why the structural fix (always creating the FNHE) was needed.

Exploit ScenarioDerived

An off-path attacker who cannot observe the victim's traffic wants to learn the ephemeral source port of a UDP connection (for example to then spoof DNS or other UDP responses). The attacker sends ICMP Fragmentation-Needed or Redirect messages that quote a UDP packet with guessed port values; because the kernel creates an observable FNHE before attempting to match a socket, a correct guess leaves a detectable change in the exception cache that the attacker can probe to confirm the port. No public exploit was identified at time of analysis, and the side-channel nature (AC:H) means it requires repeated probing rather than a single request.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 24, 2026

Linux kernel IPv4 handling of ICMP Fragmentation-Needed and Redirect messages that quote a UDP packet creates a FIB nexthop exception (FNHE) only after the quoted packet is matched to an existing socket, so an unauthenticated remote attacker operating off-path can use the presence or absence of that cache entry as a side channel to discover the ephemeral port of a connected UDP socket. The leak is probabilistic and requires repeated guesses and observation rather than a single deterministic request, and the assessed impact is confidentiality-only: the attacker learns a port number, which is primarily useful as a precursor to off-path injection rather than for direct host compromise. The issue is fixed in Linux 7.2.11 and 7.3 (stable commits be4fd05398f2b5e42029be70ee875fc749b8ce3a and 4c3499f79f8c7e8561266bcc220a18538cec0458); EPSS is 0.21% (11th percentile), there is no KEV listing, and no public exploit was identified at time of analysis.

RemediationAI

Vendor-released patch: Linux 7.2.11 and Linux 7.3, delivered through the stable commits be4fd05398f2b5e42029be70ee875fc749b8ce3a and 4c3499f79f8c7e8561266bcc220a18538cec0458 (see https://git.kernel.org/stable/c/be4fd05398f2b5e42029be70ee875fc749b8ce3a, https://git.kernel.org/stable/c/4c3499f79f8c7e8561266bcc220a18538cec0458 and https://nvd.nist.gov/vuln/detail/CVE-2026-99077). Update to 7.2.11 or 7.3, or cherry-pick the referenced stable commit into the kernel branch in use; because the fix changes exception creation ordering, expect a modest additional route lookup on the matched-socket path and, where the no-socket helper and the socket resolve to different nexthops, a second FNHE for the same destination IP - worth noting if you monitor exception cache growth. The supplied sources do not describe a validated workaround short of applying the fix; until the update is deployed, the exposure is confined to hosts that locally process attacker-supplied ICMP Fragmentation-Needed or Redirect messages quoting UDP traffic, and the practical countermeasure available from the evidence is to control which ICMP error and redirect types reach such hosts at the network boundary.

Affected VersionsENISA

Linux patch: 0
Linux 4895c771c7f006b4b90f9d6b1d2210939ba57b38 <be4fd05398f2b5e42029be70ee875fc749b8ce3a
Linux patch: 7.2.11
Linux 3.6
Linux 4895c771c7f006b4b90f9d6b1d2210939ba57b38 <4c3499f79f8c7e8561266bcc220a18538cec0458
Linux patch: 7.3

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

When the IPv4 stack locally processes an ICMP Fragmentation Needed or Redirect message, it extracts the quoted packet and normally calls ipv4_sk_update_pmtu() / ipv4_sk_redirect(), which first try to attribute the quoted datagram to a socket and only then install a FIB nexthop exception (FNHE) in the per-nexthop exception cache. Because no FNHE is created for quoted UDP packets that fail socket matching, an off-path attacker can probe the cache and infer whether a guessed ephemeral port matched a live connected socket. Earlier hardening made the FNHE hash harder to collide (commit 6457378fe796, siphash instead of Jenkins in fnhe_hashfun()) and randomized how many exceptions a bucket can hold (commit 67d6d681e15b), but both mitigations are bypassable, which is why the condition applies to hardened kernels as well. The fix reverses the ordering: ipv4_update_pmtu() and ipv4_redirect() - the helpers previously used only for quoted packets that did not originate from a socket - are invoked before socket matching, with an oif of 0 (the same convention used by icmp_err() and by the socket path for sockets not bound to a device), so every guess, right or wrong, creates or updates an observable FNHE. The patch commit notes two accepted costs in the matched-socket case: an extra route lookup, and creation of two exceptions for the same destination IP when the no-socket helper and the socket resolve to different nexthops. No CWE identifier is assigned in the available data; the trigger is the local processing of attacker-supplied ICMP error/redirect messages quoting UDP traffic.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 3.7 LOW

Remote off-path probing (AV:N, PR:N, UI:N) that is a difficult side-channel (AC:H) and discloses only an ephemeral port, so C:L and no direct integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

4
CVSS changed
Oct 24, 2026 - 14:22 NVD
7.4 (HIGH)
Patch available
Oct 23, 2026 - 13:17 EUVD
CVE Published
Oct 23, 2026 - 12:23 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 23, 2026 - 12:23 cve.org
HIGH 7.4

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

ipv4: udp: Create exceptions before socket matching

Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.

This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.

Commit 6457378fe796 ("ipv4: use siphash instead of Jenkins in fnhe_hashfun()") and commit 67d6d681e15b ("ipv4: make exception cache less predictible") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.

Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.

This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.

Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.

Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.

Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.

Executive ViewAI

Why It Matters

The Linux kernel vulnerability CVE-2026-99077 enables an off-path attacker to probabilistically discover ephemeral ports of connected UDP sockets, potentially facilitating off-path injection. This primarily threatens service availability and integrity for network services relying on UDP, requiring immediate patching to maintain trusted network communications.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Ubiquitous
Linux kernel IPv4/UDP stack present in virtually all Linux deployments
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy