CVE-2024-40923
A bug in the Linux kernel’s vmxnet3 network driver can cause the system to crash when the driver fails to allocate memory for a data ring. The issue is triggered by malformed network traffic and can lead to a kernel panic. The problem has been fixed in newer kernel releases.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Linux kernel, including versions 6.3 and 6.10, and any other releases that contain the vmxnet3 driver.
Real-world impact
An attacker could send specially crafted packets to a vulnerable system, causing the kernel to crash and the machine to become unresponsive. This results in a denial‑of‑service condition that requires a reboot to recover.
Why this severity
The CVSS score of 9.8 reflects that the vulnerability can be exploited remotely over the network, requires no user interaction, and provides complete compromise of confidentiality, integrity, and availability. The lack of authentication or privilege escalation makes it highly dangerous.
What to do about it
- 01Upgrade the Linux kernel to a version that includes the vmxnet3 driver fix (e.g., 6.10 or later).
- 02Reboot the system to load the updated kernel.
NVD-referenced vendor advisory
Timeline
- Jul 12, 2024 · Jul 12, 2024PublishedDisclosed and added to the National Vulnerability Database.
- Aug 4, 2026 · 2d agoAdvisory updatedThe NVD record was last revised.
- Aug 5, 2026 · 1d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.