Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99072

ipv4: stop route notification sizing when nexthop group shrinks

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: stop route notification sizing when nexthop group shrinks Commit 680aea08e78c ("net: ipv4: Emit notification when fib hardware flags are changed") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications. fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it. Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < 96f3fbb8575593657c7e80786dc3251d2fe3931b
    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < 81f0deb02a5b5477f236bbbaed1149b779a8632b
    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < 72d9d17092bb37b0717f12042a0817d01a1f9e78
    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < ad1c9f1b98c92609e9bb2ae8f05916defc3b0a54
    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < c1f48d1c2d5e9efd904dbbc2f2b3d41543e55c49
    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < ad2b3a68b8a7d5d27de88e05674e4adb1ce46d88
    • affected 680aea08e78c003292415518ad270bc20f9c80b1 – < d3daa33c7af92e38f2274bbd2576f58bfbaf89e6
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99072 badge
[![CVE-2026-99072](https://cveledger.app/badge/CVE-2026-99072.svg)](https://cveledger.app/cve/CVE-2026-99072)

Record last updated .