Kernel-memory disclosure via uncleared message-node padding
Published Jan 9, 2024 · Updated Nov 7, 2025
Information disclosure in the Linux kernel before 6.4-rc6 allows local users with privileged device access to read kernel memory. vhost_new_msg() allocates a vhost_msg_node with kmalloc() but clears only its msg member, leaving structure padding uninitialized for later delivery. Exploitation requires privileged read access to /dev/vhost-net; the bounded impact is residual kernel-memory disclosure with no reported write or service interruption.
Summary
What happened
Information disclosure in the Linux kernel before 6.4-rc6 allows local users with privileged device access to read kernel memory. vhost_new_msg() allocates a vhost_msg_node with kmalloc() but clears only its msg member, leaving structure padding uninitialized for later delivery. Exploitation requires privileged read access to /dev/vhost-net; the bounded impact is residual kernel-memory disclosure with no reported write or service interruption.
The record
- CVE
- CVE-2024-0340
- Published
- Jan 9, 2024
- Updated
- Nov 7, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-200, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Nov 7, 2025Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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