{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98841 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98841 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98841 and fix it if it is affected.\n\nWhat it is: CVE-2026-98841 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98841 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98841/ (Markdown: https://insights.sbomify.com/CVE-2026-98841/index.md)","id":"CVE-2026-98841","markdown":"https://insights.sbomify.com/CVE-2026-98841/index.md","name":"CVE-2026-98841","record":{"aliases":["BELL-CVE-2026-98841","DEBIAN-CVE-2026-98841","GHSA-p8pc-3hw3-fwp9","UBUNTU-CVE-2026-98841"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel vmgenid driver causes a NULL pointer dereference and kernel panic when an interrupt fires before driver data is initialized.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"virt: vmgenid: set driver_data before registering notification handlers","id":"CVE-2026-98841","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"module: fix lost error code from codetag_load_module()","id":"CVE-2026-98842"},"packages":[],"prev":{"headline":"vc_screen: reload vc pointer before if (ret) in vcs_write() to avoid UAF","id":"CVE-2026-98840"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel vmgenid driver causes a NULL pointer dereference and kernel panic when an interrupt fires before driver data is initialized.","url":"https://insights.sbomify.com/CVE-2026-98841/"}