Skip to content
Threat Brief

← All advisories

CVE-2026-99077

High 7.4No known exploitationFix available

ipv4: udp: Create exceptions before socket matching

Record last updated

CVSS score

7.4

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 38% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before be4fd05398f2b5e42029be70ee875fc749b8ce3abe4fd05398f2b5e42029be70ee875fc749b8ce3aCVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before ecd7ead4bf05e221e90f18a29aec570a50fd1592ecd7ead4bf05e221e90f18a29aec570a50fd1592CVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before 4c3499f79f8c7e8561266bcc220a18538cec04584c3499f79f8c7e8561266bcc220a18538cec0458CVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before e8f211a37396f1684af9ac81b3fc53538eb9c2f7e8f211a37396f1684af9ac81b3fc53538eb9c2f7CVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before 9f97b01ee799bdf57d9183623f3987c8bbfd4f6f9f97b01ee799bdf57d9183623f3987c8bbfd4f6fCVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before e0cd4942831d4ef8f6d4b90b0d3510460fdfbcebe0cd4942831d4ef8f6d4b90b0d3510460fdfbcebCVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before 0cf0ff2f728f2a1434c56c0bcf267fe230abf1240cf0ff2f728f2a1434c56c0bcf267fe230abf124CVE Program
LinuxLinuxfrom 4895c771c7f006b4b90f9d6b1d2210939ba57b38 before 3b92e4349c6b0dd1e05d5f0483e71ef37691b1c33b92e4349c6b0dd1e05d5f0483e71ef37691b1c3CVE Program
LinuxLinux3.6Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documented6.6.161.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0Not documented0:6.18.62-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 5.10.273 up to and including 5.10.*Not documentedCVE Program
LinuxLinux (unaffected)from 5.15.224 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.191 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.115 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.59 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.161 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.11 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 3.6Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Advisory change

    Microsoft advisory revised (7.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  9. Advisory change

    Microsoft advisory revised (8.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  10. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references