Linux Kernel up to 6.1.141/6.6.93/6.12.33/6.15.2/6.16-rc1 ACPI for_each_possible_cpu null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.141/6.6.93/6.12.33/6.15.2/6.16-rc1. Impacted is the function for_each_possible_cpu of the component ACPI. The manipulation leads to null pointer dereference. This vulnerability is listed as CVE-2025-38113. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.1.141/6.6.93/6.12.33/6.15.2/6.16-rc1. It has been rated as critical. This issue affects the function for_each_possible_cpu of the component ACPI. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Fix NULL pointer dereference when nosmp is used With nosmp in cmdline, other CPUs are not brought up, leaving their cpc_desc_ptr NULL. CPU0's iteration via for_each_possible_cpu() dereferences these NULL pointers, causing panic. Panic backtrace: [ 0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8 ... [ 0.403255] [<ffffffff809a5818>] cppc_allow_fast_switch+0x6a/0xd4 ... Kernel panic - not syncing: Attempted to kill init! [ rjw: New subject ]

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-38113 since 04/16/2025. The exploitation is known to be difficult. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 243500 (Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-1111)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.142, 6.6.94, 6.12.34, 6.15.3 or 6.16-rc2 eliminates this vulnerability. Applying the patch 356d09c7f5bf525086002a34f8bae40b134d1611/c6dad167aade4bf0bef9130f2f149f4249fc4ad0/32a48db4cf28ea087214c261da8476db218d08bd/1a677d0ceb4a5d62117b711a8b2e0aee80d33015/15eece6c5b05e5f9db0711978c3e3b7f1a2cfe12 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (243500), EUVD (EUVD-2025-19830) and CERT Bund (WID-SEC-2025-1452). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Dell Avamar
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.1
VulDB Meta Temp Score: 5.0

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 243500
Nessus Name: Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-1111)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.142/6.6.94/6.12.34/6.15.3/6.16-rc2
Patch: 356d09c7f5bf525086002a34f8bae40b134d1611/c6dad167aade4bf0bef9130f2f149f4249fc4ad0/32a48db4cf28ea087214c261da8476db218d08bd/1a677d0ceb4a5d62117b711a8b2e0aee80d33015/15eece6c5b05e5f9db0711978c3e3b7f1a2cfe12

Timelineinfo

04/16/2025 CVE reserved
07/03/2025 +78 days Advisory disclosed
07/03/2025 +0 days VulDB entry created
12/18/2025 +168 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38113 (🔒)
GCVE (CVE): GCVE-0-2025-38113
GCVE (VulDB): GCVE-100-314693
EUVD: 🔒
CERT Bund: WID-SEC-2025-1452 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 07/03/2025 11:40
Updated: 12/18/2025 01:39
Changes: 07/03/2025 11:40 (59), 07/03/2025 14:51 (1), 08/05/2025 11:28 (2), 08/23/2025 16:30 (7), 09/21/2025 15:38 (1), 11/09/2025 11:48 (1), 12/06/2025 03:20 (1), 12/18/2025 01:39 (13)
Complete: 🔍
Cache ID: 216:1E3:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!