CVE-2024-55916: Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet
Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.76.1-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.15.176.3-1 - Upgrade
Upgrade
Linux kernel (Hyper-V hv_utils / hv_vmbus)to a version that resolves this vulnerability.Patch Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet - Configuration
In util_probe(), reorder the steps so the char dev entry used by the KVP (and VSS) daemon is not created until after vmbus_open() has completed; this avoids invoking the KVP/VSS channel callback before the VMBus channel ringbuffer is initialized (prevents NULL pointer dereference in hv_pkt_iter_first).
Hyper-V hv_utils util_probe() / VMBus char dev creation path Reorder initialization steps so the KVP/VSS char dev entry is created only after vmbus_open() completes = Create /dev/vmbus/hv_kvp (KVP daemon char dev entry used by kvp_on_msg()) only after vmbus_open() has completed and after ringbuffer initialization (after first hv_ringbuffer_init)
Event History
Frequently Asked Questions
What is the severity of CVE-2024-55916?
CVE-2024-55916 has been classified as a potentially impactful vulnerability affecting the Linux kernel.
How do I fix CVE-2024-55916?
To fix CVE-2024-55916, update your Linux kernel to a version that is not affected by the vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-55916?
CVE-2024-55916 affects several Linux kernel versions between 4.9 and 6.13-rc3.
What impact does CVE-2024-55916 have on system stability?
CVE-2024-55916 can lead to system panics if the KVP or VSS daemon is started before the VMBus channel's ringbuffer is fully initialized.
Is there a workaround for CVE-2024-55916 if I cannot update the kernel?
There are currently no widely recommended workarounds for CVE-2024-55916 other than applying the kernel update.