https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:53:28 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53273 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Drivers: vmbus: Check for channel allocation before looking up relids</p> <p>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.</p> <p>Print a warning and error out in relid2channel() for a channel id that&#39;s invalid in the second kernel.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Drivers: vmbus: Check for channel allocation before looking up relids</p> <p>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.</p> <p>Print a warning and error out in relid2channel() for a channel id that&#39;s invalid in the second kernel.</p> https://vulnerability.circl.lu/vuln/cve-2023-53273