Kernel panic via unreleased transaction identifier
Published Apr 1, 2025 · Updated Aug 5, 2026
Invalid memory access in the Linux kernel allows local users to trigger a kernel panic through delayed SlimBus interrupts. slim_do_transfer() returns after a timeout without freeing its transaction identifier, so qcom_slim_ngd_rx_msgq_cb() later uses an invalid identifier during message receipt. Reachability requires local low-privileged access and the Qualcomm SlimBus NGD path; the fatal interrupt exception stops the system.
Summary
What happened
Invalid memory access in the Linux kernel allows local users to trigger a kernel panic through delayed SlimBus interrupts. slim_do_transfer() returns after a timeout without freeing its transaction identifier, so qcom_slim_ngd_rx_msgq_cb() later uses an invalid identifier during message receipt. Reachability requires local low-privileged access and the Qualcomm SlimBus NGD path; the fatal interrupt exception stops the system.
The record
- CVE
- CVE-2025-21914
- Published
- Apr 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.16
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <09d34c4cbc38485c7514069f25348e439555b282
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <0c541c8f6da23e0b92f0a6216d899659a7572074
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <18ae4cee05c310c299ba75d7477dcf34be67aa16
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <6abf3d8bb51cbaf886c3f08109a0462890b10db6
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <a32e5198a9134772eb03f7b72a7849094c55bda9
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <cec8c0ac173fe5321f03fdb1a09a9cb69bc9a9fe
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a
- Affected versionversion=afbdcc7c384b0d446da08b1e0901dc176b41b9e0 <faac8e894014e8167471a8e4a5eb35a8fefbb82a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo