Local service interruption via CAAM shutdown type confusion
Published Dec 29, 2024 · Updated May 11, 2026
Type confusion in the Linux CAAM Queue Interface in affected 5.5 and later branches allows local users to interrupt system service. The caam_qi_init registration passes a struct device pointer to caam_qi_shutdown, which interprets it as struct caam_drv_private and fails to release resources correctly. Reachability requires the CAAM Queue Interface driver and execution of its shutdown or registration-reset path; the published consequence is limited to availability.
Summary
What happened
Type confusion in the Linux CAAM Queue Interface in affected 5.5 and later branches allows local users to interrupt system service. The caam_qi_init registration passes a struct device pointer to caam_qi_shutdown, which interprets it as struct caam_drv_private and fails to release resources correctly. Reachability requires the CAAM Queue Interface driver and execution of its shutdown or registration-reset path; the published consequence is limited to availability.
The record
- CVE
- CVE-2024-56754
- Published
- Dec 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 29, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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.5
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <1f8e2f597b918ca5827a5c6d00b819d064264d1c
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <6187727e57aec122c8a99c464c74578c810cbe40
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <66eddb8dcb61065c53098510165f14b54232bcc2
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <84a185aea7b83f620699de0ea36907d588d89cf6
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <ad39df0898d3f469776c19d99229be055cc2dcea
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <ad980b04f51f7fb503530bd1cb328ba5e75a250e
- Affected versionversion=f414de2e2fffd89c8a4e5b5e06b0eba5f9d8b1eb <cc386170b3312fd7b5bc4a69a9f52d7f50814526
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.
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