Kernel crash via repeated MCB device free
Published May 8, 2025 · Updated May 11, 2026
Double free in the Linux kernel MCB parser allows local users to crash the kernel through a failed MCB device registration. When mcb_device_register() fails, put_device() releases mdev, but chameleon_parse_gdd() follows its error path and frees the same object again. Reachability requires CAP_SYS_MODULE or CAP_SYS_ADMIN and a device_add() failure that is not attacker-controllable; the grounded consequence is service interruption.
Summary
What happened
Double free in the Linux kernel MCB parser allows local users to crash the kernel through a failed MCB device registration. When mcb_device_register() fails, put_device() releases mdev, but chameleon_parse_gdd() follows its error path and frees the same object again. Reachability requires CAP_SYS_MODULE or CAP_SYS_ADMIN and a device_add() failure that is not attacker-controllable; the grounded consequence is service interruption.
The record
- CVE
- CVE-2025-37817
- Published
- May 8, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 8, 2025CVE 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=3.15
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <4ffe8c9fb561e4427dd1a3056cd5b3685b74f78d
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <59f993cd36b6e28a394ba3d977e8ffe5c9884e3b
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <7c7f1bfdb2249f854a736d9b79778c7e5a29a150
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <96838eb1836fd372e42be5db84f0b333b65146a6
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <bcc7d58ee5173e34306026bd01e1fbf75e169d37
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <c5b8a549ef1fcc6066b037a3962c79d60465ba0b
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <d70184958b0ea8c0fd52e2b456654b503e769fc8
- Affected versionversion=3764e82e5150d87b205c10cd78a9c9ab86fbfa51 <df1a5d5c6134224f9298e5189230f9d29ae50cac
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.
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