Answer in brief
CVE-2026-72451 records a Unknown severity vulnerability in xfrm: Fix xfrm state cache insertion race. 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 | >=5e4334dc39443645415450163ff5ff1ee7e79784 <6dab4dec9a49121d079981ac913569f232c06b06 || >=81a331a0e72ddc2f75092603d9577bd1a0ca23ad <a1a3360a0c44b8b5c134db2a9d0667b61c9cf523 || >=81a331a0e72ddc2f75092603d9577bd1a0ca23ad <041859fd55c81ea55e76d051e39b7b79975b8c7d || >=81a331a0e72ddc2f75092603d9577bd1a0ca23ad <ddd3d0132920319ac426e12456013eadbae67e15 || >=6.12.13 <6.12.97 | 6dab4dec9a49121d079981ac913569f232c06b06, a1a3360a0c44b8b5c134db2a9d0667b61c9cf523, 041859fd55c81ea55e76d051e39b7b79975b8c7d, ddd3d0132920319ac426e12456013eadbae67e15, 6.12.97 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: Fix xfrm state cache insertion race The xfrm input state cache insertion code checks the validity of the state before acquiring the global xfrm_state_lock. Thus it's possible for someone else to kill the state after it passed the validity check, and then the insertion will add the dead state to the cache. Fix this by moving the validity check inside the lock. This entire function is called on the input path, where BH must be off (e.g., the caller of this function xfrm_input acquires its spinlocks without disabling BH). So there is no need to disable BH here or take the RCU read lock. Remove both and replace them with an assertion that trips if BH is accidentally enabled on some future calling path.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72451 records a Unknown severity vulnerability in xfrm: Fix xfrm state cache insertion race. 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 | >=5e4334dc39443645415450163ff5ff1ee7e79784 <6dab4dec9a49121d079981ac913569f232c06b06 || >=81a331a0e72ddc2f75092603d9577bd1a0ca23ad <a1a3360a0c44b8b5c134db2a9d0667b61c9cf523 || >=81a331a0e72ddc2f75092603d9577bd1a0ca23ad <041859fd55c81ea55e76d051e39b7b79975b8c7d || >=81a331a0e72ddc2f75092603d9577bd1a0ca23ad <ddd3d0132920319ac426e12456013eadbae67e15 || >=6.12.13 <6.12.97 | 6dab4dec9a49121d079981ac913569f232c06b06, a1a3360a0c44b8b5c134db2a9d0667b61c9cf523, 041859fd55c81ea55e76d051e39b7b79975b8c7d, ddd3d0132920319ac426e12456013eadbae67e15, 6.12.97 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: Fix xfrm state cache insertion race The xfrm input state cache insertion code checks the validity of the state before acquiring the global xfrm_state_lock. Thus it's possible for someone else to kill the state after it passed the validity check, and then the insertion will add the dead state to the cache. Fix this by moving the validity check inside the lock. This entire function is called on the input path, where BH must be off (e.g., the caller of this function xfrm_input acquires its spinlocks without disabling BH). So there is no need to disable BH here or take the RCU read lock. Remove both and replace them with an assertion that trips if BH is accidentally enabled on some future calling path.
Quoted source text, attributed separately from HOL analysis.