{"api_version":"1","generated_at":"2026-10-21T16:51:54+00:00","cve":"CVE-2026-98841","urls":{"html":"https://cve.report/CVE-2026-98841","api":"https://cve.report/api/cve/CVE-2026-98841.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98841","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98841"},"summary":{"title":"virt: vmgenid: set driver_data before registering notification handlers","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirt: vmgenid: set driver_data before registering notification handlers\n\nBoth probe paths register their notification handler before assigning\ndriver_data, which the handler dereferences.\n\nIn the devicetree path, the notification IRQ can fire as soon as\ndevm_request_irq() registers the handler: the interrupt may already be\npending at probe time, for example when a VMM injects the\ngeneration-changed notification while restoring a guest from a snapshot\nthat was taken before the driver had probed (Firecracker does exactly\nthis on snapshot restore). The IRQ is also requested with IRQF_SHARED,\nso another device sharing the line can trigger the handler just as\nearly. The handler then calls vmgenid_notify(), which dereferences the\nstill-NULL driver_data and panics:\n\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.38+ #1 PREEMPT(none)\n  Hardware name: linux,dummy-virt (DT)\n  pc : vmgenid_notify.isra.0+0x24/0x8c\n  lr : vmgenid_of_irq_handler+0x14/0x34\n  Call trace:\n   vmgenid_notify.isra.0+0x24/0x8c (P)\n   vmgenid_of_irq_handler+0x14/0x34\n   __handle_irq_event_percpu+0x44/0x1bc\n   handle_irq_event+0x4c/0xb4\n   handle_fasteoi_irq+0xf8/0x1f8\n\nThe ACPI path has the same ordering problem: the handler is installed\nwith acpi_install_notify_handler() before driver_data is assigned.\nACPI notifications are dispatched asynchronously from a workqueue, so\nthe window is narrow, but a notification arriving between the two calls\nhits the same NULL dereference.\n\nAssign driver_data before registering the handlers. The state is fully\ninitialized at that point, so the handlers are safe to run. Should\nregistration fail, the probe error path leaves no dangling pointer\nbehind: the driver core clears driver_data in device_unbind_cleanup().","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:38","updated_at":"2026-10-19 10:19:48"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47","name":"https://git.kernel.org/stable/c/7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9f8139c6145cf17d690d6c414d43b4c0bef632fb","name":"https://git.kernel.org/stable/c/9f8139c6145cf17d690d6c414d43b4c0bef632fb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8f42954ad8bf9bdbf574f2c437ad30cb2601f401","name":"https://git.kernel.org/stable/c/8f42954ad8bf9bdbf574f2c437ad30cb2601f401","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/538fe5efaa9704ad820ba34b4f9df135ca873d79","name":"https://git.kernel.org/stable/c/538fe5efaa9704ad820ba34b4f9df135ca873d79","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98841","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98841","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e07606713a908eee8099883c8c830ebe33aaf748 538fe5efaa9704ad820ba34b4f9df135ca873d79 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e07606713a908eee8099883c8c830ebe33aaf748 7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e07606713a908eee8099883c8c830ebe33aaf748 8f42954ad8bf9bdbf574f2c437ad30cb2601f401 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e07606713a908eee8099883c8c830ebe33aaf748 9f8139c6145cf17d690d6c414d43b4c0bef632fb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.113 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.56 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.10 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/virt/vmgenid.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"538fe5efaa9704ad820ba34b4f9df135ca873d79","status":"affected","version":"e07606713a908eee8099883c8c830ebe33aaf748","versionType":"git"},{"lessThan":"7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47","status":"affected","version":"e07606713a908eee8099883c8c830ebe33aaf748","versionType":"git"},{"lessThan":"8f42954ad8bf9bdbf574f2c437ad30cb2601f401","status":"affected","version":"e07606713a908eee8099883c8c830ebe33aaf748","versionType":"git"},{"lessThan":"9f8139c6145cf17d690d6c414d43b4c0bef632fb","status":"affected","version":"e07606713a908eee8099883c8c830ebe33aaf748","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/virt/vmgenid.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.10"},{"lessThan":"6.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.113","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.56","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.113","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.56","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.10","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirt: vmgenid: set driver_data before registering notification handlers\n\nBoth probe paths register their notification handler before assigning\ndriver_data, which the handler dereferences.\n\nIn the devicetree path, the notification IRQ can fire as soon as\ndevm_request_irq() registers the handler: the interrupt may already be\npending at probe time, for example when a VMM injects the\ngeneration-changed notification while restoring a guest from a snapshot\nthat was taken before the driver had probed (Firecracker does exactly\nthis on snapshot restore). The IRQ is also requested with IRQF_SHARED,\nso another device sharing the line can trigger the handler just as\nearly. The handler then calls vmgenid_notify(), which dereferences the\nstill-NULL driver_data and panics:\n\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.38+ #1 PREEMPT(none)\n  Hardware name: linux,dummy-virt (DT)\n  pc : vmgenid_notify.isra.0+0x24/0x8c\n  lr : vmgenid_of_irq_handler+0x14/0x34\n  Call trace:\n   vmgenid_notify.isra.0+0x24/0x8c (P)\n   vmgenid_of_irq_handler+0x14/0x34\n   __handle_irq_event_percpu+0x44/0x1bc\n   handle_irq_event+0x4c/0xb4\n   handle_fasteoi_irq+0xf8/0x1f8\n\nThe ACPI path has the same ordering problem: the handler is installed\nwith acpi_install_notify_handler() before driver_data is assigned.\nACPI notifications are dispatched asynchronously from a workqueue, so\nthe window is narrow, but a notification arriving between the two calls\nhits the same NULL dereference.\n\nAssign driver_data before registering the handlers. The state is fully\ninitialized at that point, so the handlers are safe to run. Should\nregistration fail, the probe error path leaves no dangling pointer\nbehind: the driver core clears driver_data in device_unbind_cleanup()."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:26:33.492Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/538fe5efaa9704ad820ba34b4f9df135ca873d79"},{"url":"https://git.kernel.org/stable/c/7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47"},{"url":"https://git.kernel.org/stable/c/8f42954ad8bf9bdbf574f2c437ad30cb2601f401"},{"url":"https://git.kernel.org/stable/c/9f8139c6145cf17d690d6c414d43b4c0bef632fb"}],"title":"virt: vmgenid: set driver_data before registering notification handlers","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98841","datePublished":"2026-10-18T15:50:15.224Z","dateReserved":"2026-09-25T10:25:14.373Z","dateUpdated":"2026-10-19T09:26:33.492Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:38","lastModifiedDate":"2026-10-19 10:19:48","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98841","Ordinal":"1","Title":"virt: vmgenid: set driver_data before registering notification h","CVE":"CVE-2026-98841","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98841","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirt: vmgenid: set driver_data before registering notification handlers\n\nBoth probe paths register their notification handler before assigning\ndriver_data, which the handler dereferences.\n\nIn the devicetree path, the notification IRQ can fire as soon as\ndevm_request_irq() registers the handler: the interrupt may already be\npending at probe time, for example when a VMM injects the\ngeneration-changed notification while restoring a guest from a snapshot\nthat was taken before the driver had probed (Firecracker does exactly\nthis on snapshot restore). The IRQ is also requested with IRQF_SHARED,\nso another device sharing the line can trigger the handler just as\nearly. The handler then calls vmgenid_notify(), which dereferences the\nstill-NULL driver_data and panics:\n\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.38+ #1 PREEMPT(none)\n  Hardware name: linux,dummy-virt (DT)\n  pc : vmgenid_notify.isra.0+0x24/0x8c\n  lr : vmgenid_of_irq_handler+0x14/0x34\n  Call trace:\n   vmgenid_notify.isra.0+0x24/0x8c (P)\n   vmgenid_of_irq_handler+0x14/0x34\n   __handle_irq_event_percpu+0x44/0x1bc\n   handle_irq_event+0x4c/0xb4\n   handle_fasteoi_irq+0xf8/0x1f8\n\nThe ACPI path has the same ordering problem: the handler is installed\nwith acpi_install_notify_handler() before driver_data is assigned.\nACPI notifications are dispatched asynchronously from a workqueue, so\nthe window is narrow, but a notification arriving between the two calls\nhits the same NULL dereference.\n\nAssign driver_data before registering the handlers. The state is fully\ninitialized at that point, so the handlers are safe to run. Should\nregistration fail, the probe error path leaves no dangling pointer\nbehind: the driver core clears driver_data in device_unbind_cleanup().","Type":"Description","Title":"virt: vmgenid: set driver_data before registering notification h"}]}}}