Kernel crash via ATA host double free
Published Jul 29, 2024 · Updated Aug 5, 2026
Double free in libata-core in the Linux kernel allows local users to crash the kernel by triggering an ATA host-allocation failure. In ata_host_alloc(), the error path releases a device-resource group whose ata_host_release() callback frees host, then kfree(host) frees the same allocation again. Reachability requires ata_port_alloc() to fail after the resource group opens; the demonstrated consequence is a kernel BUG and system interruption.
Summary
What happened
Double free in libata-core in the Linux kernel allows local users to crash the kernel by triggering an ATA host-allocation failure. In ata_host_alloc(), the error path releases a device-resource group whose ata_host_release() callback frees host, then kfree(host) frees the same allocation again. Reachability requires ata_port_alloc() to fail after the resource group opens; the demonstrated consequence is a kernel BUG and system interruption.
The record
- CVE
- CVE-2024-41087
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 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=4.17
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <010de9acbea58fbcbda08e3793d6262086a493fe
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <062e256516d7db5e7dcdef117f52025cd5c456e3
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <290073b2b557e4dc21ee74a1e403d9ae79e393a2
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <56f1c7e290cd6c69c948fcd2e2a49e6a637ec38f
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <5dde5f8b790274723640d29a07c5a97d57d62047
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <702c1edbafb2e6f9d20f6d391273b5be09d366a5
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <8106da4d88bbaed809e023cc8014b766223d6e76
- Affected versionversion=dafd6c496381c1cd1f5ba9ad953e810bdcc931bc <ab9e0c529eb7cafebdd31fe1644524e80a48b05d
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