Answer in brief
CVE-2025-38675 records a Unknown severity vulnerability in xfrm: state: initialize state_ptrs earlier in xfrm_state_find. 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 | >=a16871c7832ea6435abb6e0b58289ae7dcb7e4fc <6bf2daafc51bcb9272c0fdff2afd38217337d0d3 || >=e952837f3ddb0ff726d5b582aa1aad9aa38d024d <463562f9591742be62ddde3b426a0533ed496955 || >=e952837f3ddb0ff726d5b582aa1aad9aa38d024d <94d077c331730510d5611b438640a292097341f0 || b86dc510308d7a8955f3f47a4fea4bef887653e4 || dd4c2a174994238d55ab54da2545543d36f4e0d0 || >=6.12.13 <6.12.41 || >=6.6.120 <6.7 || >=6.13.2 <6.14 | 6bf2daafc51bcb9272c0fdff2afd38217337d0d3, 463562f9591742be62ddde3b426a0533ed496955, 94d077c331730510d5611b438640a292097341f0, 6.12.41, 6.7, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: state: initialize state_ptrs earlier in xfrm_state_find In case of preemption, xfrm_state_look_at will find a different pcpu_id and look up states for that other CPU. If we matched a state for CPU2 in the state_cache while the lookup started on CPU1, we will jump to "found", but the "best" state that we got will be ignored and we will enter the "acquire" block. This block uses state_ptrs, which isn't initialized at this point. Let's initialize state_ptrs just after taking rcu_read_lock. This will also prevent a possible misuse in the future, if someone adjusts this function.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38675 records a Unknown severity vulnerability in xfrm: state: initialize state_ptrs earlier in xfrm_state_find. 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 | >=a16871c7832ea6435abb6e0b58289ae7dcb7e4fc <6bf2daafc51bcb9272c0fdff2afd38217337d0d3 || >=e952837f3ddb0ff726d5b582aa1aad9aa38d024d <463562f9591742be62ddde3b426a0533ed496955 || >=e952837f3ddb0ff726d5b582aa1aad9aa38d024d <94d077c331730510d5611b438640a292097341f0 || b86dc510308d7a8955f3f47a4fea4bef887653e4 || dd4c2a174994238d55ab54da2545543d36f4e0d0 || >=6.12.13 <6.12.41 || >=6.6.120 <6.7 || >=6.13.2 <6.14 | 6bf2daafc51bcb9272c0fdff2afd38217337d0d3, 463562f9591742be62ddde3b426a0533ed496955, 94d077c331730510d5611b438640a292097341f0, 6.12.41, 6.7, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: state: initialize state_ptrs earlier in xfrm_state_find In case of preemption, xfrm_state_look_at will find a different pcpu_id and look up states for that other CPU. If we matched a state for CPU2 in the state_cache while the lookup started on CPU1, we will jump to "found", but the "best" state that we got will be ignored and we will enter the "acquire" block. This block uses state_ptrs, which isn't initialized at this point. Let's initialize state_ptrs just after taking rcu_read_lock. This will also prevent a possible misuse in the future, if someone adjusts this function.
Quoted source text, attributed separately from HOL analysis.