Kernel memory corruption via freed vCPU0 access
Published Mar 6, 2025 · Updated Aug 5, 2026
Use-after-free in KVM in affected Linux kernel versions allows local users with KVM access to trigger kernel memory corruption. The kvm_get_vcpu() helper clamps an invalid vCPU index to zero and returns vCPU0 before it is fully online, rather than returning NULL. If vCPU creation then fails and frees vCPU0, a later dereference accesses freed memory; the path requires local KVM access and a creation error.
Summary
What happened
Use-after-free in KVM in affected Linux kernel versions allows local users with KVM access to trigger kernel memory corruption. The kvm_get_vcpu() helper clamps an invalid vCPU index to zero and returns vCPU0 before it is fully online, rather than returning NULL. If vCPU creation then fails and frees vCPU0, a later dereference accesses freed memory; the path requires local KVM access and a creation error.
The record
- CVE
- CVE-2024-58083
- Published
- Mar 6, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2025CVE 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=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <09d50ccf0b2d739db4a485b08afe7520a4402a63
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <125da53b3c0c9d7f58353aea0076e9efd6498ba7
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <1e7381f3617d14b3c11da80ff5f8a93ab14cfc46
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <5cce2ed69b00e022b5cdf0c49c82986abd2941a8
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <7c4899239d0f70f88ac42665b3da51678d122480
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <ca8da90ed1432ff3d000de4f1e2275d4e7d21b96
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <d817e510662fd1c9797952408d94806f97a5fffd
- Affected versionversion=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c <f2f805ada63b536bc192458a7098388286568ad4
- Affected versionversion=4.14.120 <4.15
- Affected versionversion=4.19.44 <4.20
- Affected versionversion=5.0.17 <5.1
- Affected versionversion=5.1
- Affected versionversion=559e2696d2f47a3575e9550f101a7e59e30b1b38
- Affected versionversion=7cee966029037a183d98cb88251ceb92a233fe63
- Affected versionversion=d39f3cc71382165bb7efb8e06a2bd32f847de4ae
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