Answer in brief
CVE-2026-98561 records a Unknown severity vulnerability in nfp: hold IPsec RX state under the XArray lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.2 | Not reported |
| Linux/Linuxgeneric | >=57f273adbcd44172cbe0bd10b8b7408dd255699f <c1b1639fb138db52fcfbd1747e92f2454076c6d5 || >=57f273adbcd44172cbe0bd10b8b7408dd255699f <dd765023bb54f9650f8b9137906fb2c4a554dd1d || >=57f273adbcd44172cbe0bd10b8b7408dd255699f <8468d05aa08dc430b5675beadf6f6fb8943f170b || >=57f273adbcd44172cbe0bd10b8b7408dd255699f <fe6c8ea8bfd5d1253bb0de682b1fcc2c4bb92488 || >=57f273adbcd44172cbe0bd10b8b7408dd255699f <1a983a4e14c635c40354be110cd9a1a5c94e01e6 | c1b1639fb138db52fcfbd1747e92f2454076c6d5, dd765023bb54f9650f8b9137906fb2c4a554dd1d, 8468d05aa08dc430b5675beadf6f6fb8943f170b, fe6c8ea8bfd5d1253bb0de682b1fcc2c4bb92488, 1a983a4e14c635c40354be110cd9a1a5c94e01e6 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: nfp: hold IPsec RX state under the XArray lock 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.
Quoted source text, attributed separately from HOL analysis.