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-98967cxgb4/ch_ktls: disable softirqs around tid_list erases

Description

In the Linux kernel, the following vulnerability has been resolved: cxgb4/ch_ktls: disable softirqs around tid_list erases chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh(). The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH. However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs. When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task. Use xa_erase_bh() at both sites to match the insertion 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.18% · top 92% 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 b96adbf6601d76ee0bdd9bfa5bcdd0cdd5333d78 – < 2c49ea1dd16d6dc0dd895e6aec57c9a448191cfe
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < bafe51bb145e6ae549ae79dcbc35648292625934
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < 0c5063a898813a420e6bad93debd134ef8b3bfd1
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < 8739f06e3f82cd715f7dd10ab24029ed881efc90
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < bcf97573d44e277b1744d7f1226f665aa0ccc599
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < 7110c7f70c59eb7924e79853bcc00e2a026662e6
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < bea736a2b8c6da5b1078badf1206541b5404250f
    • affected 65e302a9bd57b62872040d57eea1201562a7cbb2 – < 4c9dc0faca98084922caeb689579d338cf3e1c29
    • affected 70c4ead897211b184f36cbeda213f2a3e8153218
    • affected 5.10.42 – < 5.10.273
    • affected 5.12.9 – < 5.13
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.10.273 – ≤ 5.10.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .