Freed-memory access via late QM error injection
Published Oct 21, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux Hisilicon QM driver allows local users to expose released host memory to accelerator access during reset. The driver stops a queue before injecting the QM error, so queue memory can be released while the master out-of-order engine can still access it. Reachability requires a Hisilicon PCIe crypto accelerator, an active queue, and an uncorrectable ECC fault; stale access can disclose or corrupt reused memory or crash the host.
Summary
What happened
Use-after-free in the Linux Hisilicon QM driver allows local users to expose released host memory to accelerator access during reset. The driver stops a queue before injecting the QM error, so queue memory can be released while the master out-of-order engine can still access it. Reachability requires a Hisilicon PCIe crypto accelerator, an active queue, and an uncorrectable ECC fault; stale access can disclose or corrupt reused memory or crash the host.
The record
- CVE
- CVE-2024-47730
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE 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=5.8
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <801d64177faaec184cee1e1aa4d8487df1364a54
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <85e81103033324d7a271dafb584991da39554a89
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <98d3be34c9153eceadb56de50d9f9347e88d86e4
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <aa3e0db35a60002fb34ef0e4ad203aa59fd00203
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <b04f06fc0243600665b3b50253869533b7938468
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <c5f5b813e546f7fe133539c3d7a5086cc8dd2aa1
- Affected versionversion=6c6dd5802c2d6769fa589c0e8de54299def199a7 <f8024f12752e32ffbbf59e1c09d949f977ff743f
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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