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-98625netfilter: flowtable: publish HW_DEAD after worker is done

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: publish HW_DEAD after worker is done flow_offload_work_del() sets NF_FLOW_HW_DEAD before the work handler clears NF_FLOW_HW_PENDING. Once a flow is both HW_DYING and HW_DEAD, a concurrent garbage collection pass can remove it and schedule it for RCU freeing. The offload worker holds neither an RCU read lock nor a reference to the flow. If it is preempted after publishing HW_DEAD, the RCU callback can free the flow before the worker resumes and clears HW_PENDING, resulting in a use-after-free. Move HW_DEAD publication to the common worker epilogue after the pending bit is cleared, making it the final flow access by destroy work. Order all preceding flow accesses before publishing the bit that allows garbage collection to free the object.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day 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.21% · top 89% of all CVEs (17 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 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < f92e8f39726ba68a7c42c6b7566be687c8161579
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < 00e452a7ca9fda135ea3d04a11128d5088e354a8
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < 56f39c7d139bb76072efe2fb3dcafc13ba915ad8
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < e20701843032c438f879066a77ea85e361c6b999
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < b4f0f05dfbe836a171bff261f17d098a4d5461ea
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < b0ef9450e93f2adeb77593db14c2ac7c6c8f5060
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < f26652e99f519e6bd34f8a9b48fbb33c603585f2
    • affected 2c8897953f3b2ff5498f3f275708a742bfcdbc24 – < d644b23afe1ef509c9961a6d84a093c2587edf02
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .