Kernel memory corruption via device-managed double free
Published Jan 6, 2025 · Updated May 23, 2026
Double free in Linux kernel raw NAND PMECC code allows local users to corrupt kernel memory during Atmel NAND controller setup. The atmel_pmecc_create_user function allocates its user object with devm_kzalloc, but an error path also passes that device-managed object to kfree, so device cleanup frees it again. Reachability requires an Atmel NAND controller and the failing user-object creation path; public material identifies no demonstrated code-execution outcome.
Summary
What happened
Double free in Linux kernel raw NAND PMECC code allows local users to corrupt kernel memory during Atmel NAND controller setup. The atmel_pmecc_create_user function allocates its user object with devm_kzalloc, but an error path also passes that device-managed object to kfree, so device cleanup frees it again. Reachability requires an Atmel NAND controller and the failing user-object creation path; public material identifies no demonstrated code-execution outcome.
The record
- CVE
- CVE-2024-56766
- Published
- Jan 6, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 6, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=2014fcea19ec27df033359a0f42db0e8ed4290a8
- Affected versionversion=22fbbc37edb840fd420fadf670366be9bf028426 <ca9818554b0f33e87f38e4bfa2dac056692d46cc
- Affected versionversion=24cbc37e837fd9e31e5024480b779207d1d99f1d <6ea15205d7e2b811fbbdf79783f686f58abfb4b7
- Affected versionversion=4.19.325 <4.20
- Affected versionversion=5.10.231 <5.10.233
- Affected versionversion=5.15.174 <5.15.176
- Affected versionversion=5.4.287 <5.4.289
- Affected versionversion=54cb5fa850f9306d84e49a3db44b7a7eb5536cd1 <1562871ef613fa9492aa0310933eff785166a90e
- Affected versionversion=5fe7709251e334cc27618473299c48340cecd3c8 <3d825a241e65f7e3072978729e79d735ec40b80e
- Affected versionversion=6.11.11 <6.12
- Affected versionversion=6.1.120 <6.1.123
- Affected versionversion=6.12.2 <6.12.8
- Affected versionversion=6.6.64 <6.6.69
- Affected versionversion=6d734f1bfc336aaea91313a5632f2f197608fadd <d8e4771f99c0400a1873235704b28bb803c83d17
- Affected versionversion=8ac19ec818c548c5788da5926dcc8af96fad4bb1 <d2f090ea57f8d6587e09d4066f740a8617767b3d
- Affected versionversion=bdd11a04d102f8310812aa7cec39545fdd6662d1
- Affected versionversion=f1290871c8aaeb13029390a2b6e5c05733a1be6f <dd45c87782738715d5e7c167f8dabf0814a7394a
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