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-98622net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure flow_offload_alloc() returns NULL when the conntrack entry is dying (e.g. raced with a conntrack flush) or when the GFP_ATOMIC allocation fails; both are expected under load and neither is a kernel bug. This path runs from softirq on every committed packet, so with panic_on_warn=1 an unprivileged user can panic the box just by racing a conntrack flush against a `tc ... action ct commit` classifier. Reproduced with a custom repro under QEMU: a small, fixed set of UDP flows through `tc filter ... action ct commit` on lo, raced against threads flooding bare ctnetlink CT_DELETE (flush) requests. Hits WARNING: net/sched/act_ct.c:437 (tcf_ct_flow_table_add(), inlined into tcf_ct_act() in this build) within ~15s on the unpatched kernel; same setup is clean on the patched kernel. The fix itself is behavior-preserving: both branches already did `goto err_alloc` before and after, only the WARN is removed.

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.18% · top 93% of all CVEs (16 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 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < e8fcf3f08834e939b797311742ee72b1e2a08096
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < af475f599270e59313552e6c6f3af8507da672b8
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < 424ba52c0058deeb940d02cba52eb0aeb288db33
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < d512c484bd93a5f2794aa03c9faeb7bcb82dbd4a
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < d805560ad69cb266d669341ca01e26bffb0d2c67
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < 00734f3684fcec42c319bedfe68a5d357c720b53
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < 650787233c2fd6e515a7c5f371019a9fa080ccd2
    • affected 64ff70b80fd403110b67dd9f7184a604fdb0da43 – < 47abe7a5c4eb53269aca3506446f851572a059a3
  • 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-98622 badge
[![CVE-2026-98622](https://cveledger.app/badge/CVE-2026-98622.svg)](https://cveledger.app/cve/CVE-2026-98622)

Record last updated .