Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: xfrm: state: initialize state_ptrs earlier in xfrm_state_find In case of… (CVE-2025-38675)
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.
AI Analysis
Technical Summary
This vulnerability concerns the xfrm subsystem's state management in Microsoft Azure Linux kernel 3.0, where state pointers are initialized later than appropriate in the xfrm_state_find function. This timing flaw could lead to concurrency issues as indicated by CWE-362. The Microsoft Security Response Center has acknowledged the issue but has not provided detailed patch or mitigation information. The vulnerability is classified as medium severity based on the available data.
Potential Impact
The vulnerability could potentially lead to race conditions or concurrency problems within the xfrm subsystem of the affected kernel, which may affect system stability or security. However, no known exploits have been reported, and the exact impact is not detailed in the available information.
Mitigation Recommendations
Patch status is not yet confirmed — check the Microsoft Security Response Center advisory for current remediation guidance. No official fix or workaround has been provided at this time.
Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: xfrm: state: initialize state_ptrs earlier in xfrm_state_find In case of… (CVE-2025-38675)
Description
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.
CVSS v3.1
Score 7.8high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability concerns the xfrm subsystem's state management in Microsoft Azure Linux kernel 3.0, where state pointers are initialized later than appropriate in the xfrm_state_find function. This timing flaw could lead to concurrency issues as indicated by CWE-362. The Microsoft Security Response Center has acknowledged the issue but has not provided detailed patch or mitigation information. The vulnerability is classified as medium severity based on the available data.
Potential Impact
The vulnerability could potentially lead to race conditions or concurrency problems within the xfrm subsystem of the affected kernel, which may affect system stability or security. However, no known exploits have been reported, and the exact impact is not detailed in the available information.
Mitigation Recommendations
Patch status is not yet confirmed — check the Microsoft Security Response Center advisory for current remediation guidance. No official fix or workaround has been provided at this time.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_vex
- Csaf Version
- 2.0
- Publisher
- Microsoft Security Response Center
- Advisory Id
- msrc_CVE-2025-38675
- Cve Count
- 1
Threat ID: 6a16098fe29bf47b50654d91
Added to database: 05/26/2026, 20:58:55 UTC
Last enriched: 06/29/2026, 23:50:25 UTC
Last updated: 09/10/2026, 19:36:50 UTC
Views: 95
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.