CVE-2025-40346arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
- 8 months later
· 8 months later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < 64da320252e43456cc9ec3055ff567f168467b37
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < 02fbea0864fd4a863671f5d418129258d7159f68
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < a77f8434954cb1e9c42c3854e40855fdcf5ab235
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < 3373f263bb647fcc3b5237cfaef757633b9ee25e
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < 45379303124487db3a81219af7565d41f498167f
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < 3a01b2614e84361aa222f67bc628593987e5cdb2
- affected b8fe128dad8f97cc9af7c55a264d1fc5ab677195 – < 2eead19334516c8e9927c11b448fbe512b1f18a1
- affected 5.7
- unaffected < 5.7
- unaffected 5.10.246 – ≤ 5.10.*
- unaffected 5.15.196 – ≤ 5.15.*
- unaffected 6.1.158 – ≤ 6.1.*
- unaffected 6.6.115 – ≤ 6.6.*
- unaffected 6.12.56 – ≤ 6.12.*
- unaffected 6.17.6 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References7
- https://git.kernel.org/stable/c/64da320252e43456cc9ec3055ff567f168467b37 (opens in a new tab)
- https://git.kernel.org/stable/c/02fbea0864fd4a863671f5d418129258d7159f68 (opens in a new tab)
- https://git.kernel.org/stable/c/a77f8434954cb1e9c42c3854e40855fdcf5ab235 (opens in a new tab)
- https://git.kernel.org/stable/c/3373f263bb647fcc3b5237cfaef757633b9ee25e (opens in a new tab)
- https://git.kernel.org/stable/c/45379303124487db3a81219af7565d41f498167f (opens in a new tab)
- https://git.kernel.org/stable/c/3a01b2614e84361aa222f67bc628593987e5cdb2 (opens in a new tab)
- https://git.kernel.org/stable/c/2eead19334516c8e9927c11b448fbe512b1f18a1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-203641 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40346)Record last updated .