CVE-2024-42134

What it actually does

Null pointer dereference in vp_del_vqs when vp_dev->is_avq is accessed without a NULL check on legacy virtio-pci devices that never initialize the field.

Why it matters to the business

Crashes virtual machine guests during device attach or virtqueue deletion operations, causing denial of service and potential data loss for workloads running on affected Linux kernels in virtualized environments.

How an attack unfolds

An attacker with the ability to trigger virtqueue deletion (for example via device attach operations in a guest) forces execution of vp_del_vqs on a legacy virtio-pci device; because is_avq is NULL the dereference immediately panics the guest kernel.

How to fix it

Update the Linux kernel to a version containing commit 5e2024b0b9b3d5709e3f7e9b92951d7e29154106 or later; rebuild and reboot all affected hosts and guests.

How to confirm the fix worked

Confirm the running kernel contains commit 5e2024b0b9b3d5709e3f7e9b92951d7e29154106; re-execute virsh attach-device and verify the guest remains stable without a NULL dereference panic.

Typical attack path

1. Identify a Linux guest using legacy virtio-pci transport
2. Perform an operation that deletes virtqueues such as virsh attach-device or hot-unplug
3. vp_del_vqs is invoked with a NULL is_avq pointer
4. Kernel dereferences the NULL pointer and crashes

How to detect it

Review kernel panic logs and dmesg output for NULL pointer dereference faults originating from virtio_pci_common.c in vp_del_vqs; correlate timestamps with device attach or hotplug events.

• virtio_pci_common.c: vp_del_vqs
• NULL pointer dereference in is_avq
• general protection fault in vp_del_vqs

What your security team should do

• Prioritize kernel updates on all systems using virtio-pci legacy devices within the next maintenance window
• Enable crash-dump collection to capture future kernel panics for forensic review
• Monitor vendor advisories for backported fixes in distribution kernels