Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40346: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 02fbea0864fd4a863671f5d418129258d7159f68, 2eead19334516c8e9927c11b448fbe512b1f18a1, 3373f263bb647fcc3b5237cfaef757633b9ee25e.

Low priority for now. Upgrade to Linux Linux 02fbea0864fd4a863671f5d418129258d7159f68, 2eead19334516c8e9927c11b448fbe512b1f18a1, 3373f263bb647fcc3b5237cfaef757633b9ee25e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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().

—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 14, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40346

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before 64da320252e43456cc9ec3055ff567f168467b37affected · git
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before 02fbea0864fd4a863671f5d418129258d7159f68affected · git
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before a77f8434954cb1e9c42c3854e40855fdcf5ab235affected · git
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before 3373f263bb647fcc3b5237cfaef757633b9ee25eaffected · git
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before 45379303124487db3a81219af7565d41f498167faffected · git
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before 3a01b2614e84361aa222f67bc628593987e5cdb2affected · git
    • b8fe128dad8f97cc9af7c55a264d1fc5ab677195 and later · before 2eead19334516c8e9927c11b448fbe512b1f18a1affected · git
    • before 5.7not affected · semver
    • 5.10.246 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68244Dec 16, 2025 · drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD
    0Monitor
  • ← EarlierCVE-2025-68310Dec 16, 2025 · s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump
    0Monitor
  • Later →CVE-2025-40347Dec 16, 2025 · net: enetc: fix the deadlock of enetc_mdio_lock
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux02fbea0864fd4a863671f5d418129258d7159f68Vendor (CNA)
Linux Linux2eead19334516c8e9927c11b448fbe512b1f18a1Vendor (CNA)
Linux Linux3373f263bb647fcc3b5237cfaef757633b9ee25eVendor (CNA)
Linux Linux3a01b2614e84361aa222f67bc628593987e5cdb2Vendor (CNA)
Linux Linux45379303124487db3a81219af7565d41f498167fVendor (CNA)
Linux Linux64da320252e43456cc9ec3055ff567f168467b37Vendor (CNA)
Linux Linuxa77f8434954cb1e9c42c3854e40855fdcf5ab235Vendor (CNA)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records