CVE-2025-40346 — arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()
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().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < 64da320252e43456cc9ec3055ff567f168467b37≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < 02fbea0864fd4a863671f5d418129258d7159f68≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < a77f8434954cb1e9c42c3854e40855fdcf5ab235≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < 3373f263bb647fcc3b5237cfaef757633b9ee25e≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < 45379303124487db3a81219af7565d41f498167f≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < 3a01b2614e84361aa222f67bc628593987e5cdb2≥ b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and < 2eead19334516c8e9927c11b448fbe512b1f18a1version 5.7 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- github.com/advisories/GHSA-3qw8-vgp2-684r
- git.kernel.org/stable/c/3373f263bb647fcc3b5237cfaef757633b9ee25e
- git.kernel.org/stable/c/64da320252e43456cc9ec3055ff567f168467b37
- git.kernel.org/stable/c/02fbea0864fd4a863671f5d418129258d7159f68
- git.kernel.org/stable/c/45379303124487db3a81219af7565d41f498167f
- git.kernel.org/stable/c/3a01b2614e84361aa222f67bc628593987e5cdb2
- nvd.nist.gov/vuln/detail/CVE-2025-40346
- git.kernel.org/stable/c/a77f8434954cb1e9c42c3854e40855fdcf5ab235
- git.kernel.org/stable/c/2eead19334516c8e9927c11b448fbe512b1f18a1
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-40346 is "arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.