Kernel memory corruption via duplicate STM deallocation
Published Jun 21, 2024 · Updated May 23, 2026
A double-free in Linux kernel stm_register_device() allows local users to corrupt kernel memory during failed STM device registration. On the error path, put_device(&stm->dev) invokes stm_device_release() to free stm, then the next-line vfree(stm) frees the same allocation again. Low-privileged local access is required; public sources do not identify a user-controlled trigger or a more specific runtime consequence.
Summary
What happened
A double-free in Linux kernel stm_register_device() allows local users to corrupt kernel memory during failed STM device registration. On the error path, put_device(&stm->dev) invokes stm_device_release() to free stm, then the next-line vfree(stm) frees the same allocation again. Low-privileged local access is required; public sources do not identify a user-controlled trigger or a more specific runtime consequence.
The record
- CVE
- CVE-2024-38627
- Published
- Jun 21, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2024CVE 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=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <370c480410f60b90ba3e96abe73ead21ec827b20
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <3df463865ba42b8f88a590326f4c9ea17a1ce459
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <4bfd48bb6e62512b9c392c5002c11e1e3b18d247
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <6cc30ef8eb6d8f8d6df43152264bbf8835d99931
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <713fc00c571dde4af3db2dbd5d1b0eadc327817b
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <7419df1acffbcc90037f6b5a2823e81389659b36
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <a0450d3f38e7c6c0a7c0afd4182976ee15573695
- Affected versionversion=389b6699a2aa0b457aa69986e9ddf39f3b4030fd <d782a2db8f7ac49c33b9ca3e835500a28667d1be
- Affected versionversion=4.4.178 <4.5
- Affected versionversion=4.7
- Affected versionversion=b0351a51ffda593b2b1b35dd0c00a73505edb256
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.
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