CVE-2025-40346

arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()

N/A
Published: December 16, 2025 at 01:30 PM UTC
Updated: October 14, 2026 at 01:10 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() Fix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity() which causes the code to proceed with NULL clock pointers. The current logic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both valid pointers and NULL, leading to potential NULL pointer dereference in clk_get_rate(). Per include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns: "The error code within @ptr if it is an error pointer; 0 otherwise." This means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL pointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed) when cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be called when of_clk_get() returns NULL. Replace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid pointers, preventing potential NULL pointer dereference in clk_get_rate().

Affected

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

5.7b8fe128dad8f97cc9af7c55a264d1fc5ab677195
Vendor states this is fixed in 02fbea0864fd4a863671f5d418129258d7159f68 (fixed)
Vendor states this is fixed in 2eead19334516c8e9927c11b448fbe512b1f18a1 (fixed)
Vendor states this is fixed in 3373f263bb647fcc3b5237cfaef757633b9ee25e (fixed)
Vendor states this is fixed in 3a01b2614e84361aa222f67bc628593987e5cdb2 (fixed)
Vendor states this is fixed in 45379303124487db3a81219af7565d41f498167f (fixed)
Vendor states this is fixed in 64da320252e43456cc9ec3055ff567f168467b37 (fixed)
Vendor states this is fixed in a77f8434954cb1e9c42c3854e40855fdcf5ab235 (fixed)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.196 (unaffected)
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.1.158 (unaffected)
Vendor states this is fixed in 6.12.56 (unaffected)
Vendor states this is fixed in 6.17.6 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.115 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

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