CVE-2023-53273
Drivers: vmbus: Check for channel allocation before looking up relids
Description
In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset by the host. When the second kernel boots and if the guest receives a vmbus interrupt during vmbus driver initialization before vmbus_connect() is called, before it finishes, or if it fails, the vmbus interrupt service routine is called which in turn calls relid2channel() and can cause a null pointer dereference. Print a warning and error out in relid2channel() for a channel id that's invalid in the second kernel.
INFO
Published Date :
Sept. 16, 2025, 8:11 a.m.
Last Modified :
Sept. 16, 2025, 8:11 a.m.
Remotely Exploit :
No
Source :
Linux
Affected Products
The following products are affected by CVE-2023-53273
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the latest stable version.
- Apply the specific patch for the vmbus driver vulnerability.
- Ensure the vmbus driver is properly initialized.
- Monitor system logs for related errors.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-53273 vulnerability anywhere in the article.