Skip to content
Threat Brief

← All advisories

CVE-2026-98841

Severity unknownNo known exploitationFix available

virt: vmgenid: set driver_data before registering notification handlers

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: virt: vmgenid: set driver_data before registering notification handlers Both probe paths register their notification handler before assigning driver_data, which the handler dereferences. In the devicetree path, the notification IRQ can fire as soon as devm_request_irq() registers the handler: the interrupt may already be pending at probe time, for example when a VMM injects the generation-changed notification while restoring a guest from a snapshot that was taken before the driver had probed (Firecracker does exactly this on snapshot restore). The IRQ is also requested with IRQF_SHARED, so another device sharing the line can trigger the handler just as early. The handler then calls vmgenid_notify(), which dereferences the still-NULL driver_data and panics: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.38+ #1 PREEMPT(none) Hardware name: linux,dummy-virt (DT) pc : vmgenid_notify.isra.0+0x24/0x8c lr : vmgenid_of_irq_handler+0x14/0x34 Call trace: vmgenid_notify.isra.0+0x24/0x8c (P) vmgenid_of_irq_handler+0x14/0x34 __handle_irq_event_percpu+0x44/0x1bc handle_irq_event+0x4c/0xb4 handle_fasteoi_irq+0xf8/0x1f8 The ACPI path has the same ordering problem: the handler is installed with acpi_install_notify_handler() before driver_data is assigned. ACPI notifications are dispatched asynchronously from a workqueue, so the window is narrow, but a notification arriving between the two calls hits the same NULL dereference. Assign driver_data before registering the handlers. The state is fully initialized at that point, so the handlers are safe to run. Should registration fail, the probe error path leaves no dangling pointer behind: the driver core clears driver_data in device_unbind_cleanup().

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom e07606713a908eee8099883c8c830ebe33aaf748 before 538fe5efaa9704ad820ba34b4f9df135ca873d79538fe5efaa9704ad820ba34b4f9df135ca873d79CVE Program
LinuxLinuxfrom e07606713a908eee8099883c8c830ebe33aaf748 before 7a1e8daeaa466c6aaffa223e1afe9cfeece0dd477a1e8daeaa466c6aaffa223e1afe9cfeece0dd47CVE Program
LinuxLinuxfrom e07606713a908eee8099883c8c830ebe33aaf748 before 8f42954ad8bf9bdbf574f2c437ad30cb2601f4018f42954ad8bf9bdbf574f2c437ad30cb2601f401CVE Program
LinuxLinuxfrom e07606713a908eee8099883c8c830ebe33aaf748 before 9f8139c6145cf17d690d6c414d43b4c0bef632fb9f8139c6145cf17d690d6c414d43b4c0bef632fbCVE Program
LinuxLinux6.10Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.113 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.56 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.10 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.10Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references