Look up another CVE · open CVE-2026-98561 in the interactive tracker
CVE-2026-98561
nfp: hold IPsec RX state under the XArray lock
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/net. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-98561 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.113-1 | Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
nfp_net_ipsec_rx() drops the XArray lock before taking a reference to the xfrm_state it found. The delete path can erase the entry and drop the last state reference in that interval. RX can then try to increment a zero refcount after the state has been queued for destruction. The driver queues firmware invalidation asynchronously; the delete path does not wait for the command to complete or drain pending RX processing. The XFRM garbage collector waits for an RCU grace period before freeing the state. That delays reclamation but does not make acquiring a reference from zero valid. Take the xfrm_state reference before releasing the XArray lock so xa_erase() cannot run between lookup and reference acquisition.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/net/ethernet/netronome/nfp/crypto/ipsec.c
- What this is
- NETRONOME ETHERNET DRIVERSMAINTAINERS section matched on drivers/net/ethernet/netronome/ · oss-drivers@corigine.com · Odd Fixes
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-10-18 (today)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- not scored
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/net
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.2 | 6.6.158 | c1b1639fb138 |
| 6.2 | 6.12.112 | dd765023bb54 |
| 6.2 | 6.18.55 | 8468d05aa08d |
| 6.2 | 7.2.9 | fe6c8ea8bfd5 |
| 6.2 | 7.3 | 1a983a4e14c6 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98561, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.