CVE-2026-99077 — ipv4: udp: Create exceptions before socket matching
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < be4fd05398f2b5e42029be70ee875fc749b8ce3a≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < 4c3499f79f8c7e8561266bcc220a18538cec0458version 3.6≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < ecd7ead4bf05e221e90f18a29aec570a50fd1592≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < e8f211a37396f1684af9ac81b3fc53538eb9c2f7≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < 9f97b01ee799bdf57d9183623f3987c8bbfd4f6f≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < e0cd4942831d4ef8f6d4b90b0d3510460fdfbceb≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < 0cf0ff2f728f2a1434c56c0bcf267fe230abf124 and 1 more≥ 4895c771c7f006b4b90f9d6b1d2210939ba57b38 and < 3b92e4349c6b0dd1e05d5f0483e71ef37691b1c3 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.4 | CVSS 3.1 | High | 2.2 | 5.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.4 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.4 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.37%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Affected products added · linux/linux
- CVSS changed · 7.4
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 4× References added · Oct 23, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
10 on the record
- git.kernel.org/stable/c/ecd7ead4bf05e221e90f18a29aec570a50fd1592
- git.kernel.org/stable/c/be4fd05398f2b5e42029be70ee875fc749b8ce3a
- git.kernel.org/stable/c/3b92e4349c6b0dd1e05d5f0483e71ef37691b1c3
- git.kernel.org/stable/c/e8f211a37396f1684af9ac81b3fc53538eb9c2f7
- git.kernel.org/stable/c/0cf0ff2f728f2a1434c56c0bcf267fe230abf124
- nvd.nist.gov/vuln/detail/CVE-2026-99077
- github.com/advisories/GHSA-xqqf-wrfv-j8jm
- git.kernel.org/stable/c/e0cd4942831d4ef8f6d4b90b0d3510460fdfbceb
- git.kernel.org/stable/c/9f97b01ee799bdf57d9183623f3987c8bbfd4f6f
- git.kernel.org/stable/c/4c3499f79f8c7e8561266bcc220a18538cec0458
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-99077 is "ipv4: udp: Create exceptions before socket matching", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.37% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.