CVE-2025-38008 Affecting kernel6.12-modules-extra package, versions <0:6.12.30-34.92.amzn2023


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.02% (5th 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 IDSNYK-AMZN2023-KERNEL612MODULESEXTRA-10694101
  • published11 Jul 2025
  • disclosed18 Jun 2025

Introduced: 18 Jun 2025

NewCVE-2025-38008  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel6.12-modules-extra to version 0:6.12.30-34.92.amzn2023 or higher.
This issue was patched in ALAS2023-2025-1053.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel6.12-modules-extra package and not the kernel6.12-modules-extra 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:

mm/page_alloc: fix race condition in unaccepted memory handling

The page allocator tracks the number of zones that have unaccepted memory using static_branch_enc/dec() and uses that static branch in hot paths to determine if it needs to deal with unaccepted memory.

Borislav and Thomas pointed out that the tracking is racy: operations on static_branch are not serialized against adding/removing unaccepted pages to/from the zone.

Sanity checks inside static_branch machinery detects it:

WARNING: CPU: 0 PID: 10 at kernel/jump_label.c:276 __static_key_slow_dec_cpuslocked+0x8e/0xa0

The comment around the WARN() explains the problem:

/*
 * Warn about the &#39;-1&#39; case though; since that means a
 * decrement is concurrent with a first (0-&gt;1) increment. IOW
 * people are trying to disable something that wasn&#39;t yet fully
 * enabled. This suggests an ordering problem on the user side.
 */

The effect of this static_branch optimization is only visible on microbenchmark.

Instead of adding more complexity around it, remove it altogether.

CVSS Base Scores

version 3.1