Race Condition Affecting kernel6.12-libbpf-devel package, versions <1:6.12.46-66.121.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.02% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Race Condition vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-AMZN2023-KERNEL612LIBBPFDEVEL-13168811
  • published1 Oct 2025
  • disclosed22 Aug 2025

Introduced: 22 Aug 2025

CVE-2025-38675  (opens in a new tab)
CWE-362  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel6.12-libbpf-devel to version 1:6.12.46-66.121.amzn2023 or higher.
This issue was patched in ALAS2023-2025-1208.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel6.12-libbpf-devel package and not the kernel6.12-libbpf-devel package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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 Base Scores

version 3.1