CVE-2025-38675

xfrm: state: initialize state_ptrs earlier in xfrm_state_find

MEDIUM
4.7
CVSS Score
Published: August 22, 2025 at 04:04 PM UTC
Updated: August 5, 2026 at 12:44 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.7
Exploit prediction
EPSS 0.1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.13.2v ≥ 6.6.1206.12.13 ≤ v < 6.12.416.13.2 ≤ v < 6.146.13.2 ≤ v < 6.15.96.14 ≤ v < 6.15.96.14 ≤ v < 6.166.6.120 ≤ v < 6.76.12.136.13.26.16 rc16.16 rc26.16 rc36.16 rc46.16 rc56.16 rc66.16 rc76.6.120a16871c7832ea6435abb6e0b58289ae7dcb7e4fcb86dc510308d7a8955f3f47a4fea4bef887653e4dd4c2a174994238d55ab54da2545543d36f4e0d0e952837f3ddb0ff726d5b582aa1aad9aa38d024d
Vendor states this is fixed in 463562f9591742be62ddde3b426a0533ed496955 (fixed)
Vendor states this is fixed in 6bf2daafc51bcb9272c0fdff2afd38217337d0d3 (fixed)
Vendor states this is fixed in 94d077c331730510d5611b438640a292097341f0 (fixed)
Vendor states this is fixed in 6.12.41 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.15.9 (unaffected)
Vendor states this is fixed in 6.16 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/463562f9591742be62ddde3b426a0533ed496955
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6bf2daafc51bcb9272c0fdff2afd38217337d0d3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/94d077c331730510d5611b438640a292097341f0

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card