# CVE-2026-98967: cxgb4/ch_ktls: disable softirqs around tid_list erases


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110783, BELL-CVE-2026-98967, DEBIAN-CVE-2026-98967, GHSA-hvvf-g7gg-pmx4, UBUNTU-CVE-2026-98967

## What is CVE-2026-98967?

CVE-2026-98967 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-98967?


## How do I fix CVE-2026-98967?

Upgrade to a fixed version.

## Is CVE-2026-98967 being exploited?

There is no known exploitation of CVE-2026-98967 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98967 and fix it if it is affected.

What it is: CVE-2026-98967 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98967 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98967/ (Markdown: https://insights.sbomify.com/CVE-2026-98967/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98967
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98967
- OSV: https://osv.dev/vulnerability/CVE-2026-98967

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98967/
Summaries are generated and may contain mistakes; the official description above is the record.