CVE-2026-98841: Linux kernel · virt: vmgenid: set driver_data before registering notification handlers
Source GCVE Database
Not known to be exploited · fixed in 538fe5efaa9704ad820ba34b4f9df135ca873d79 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 538fe5efaa9704ad820ba34b4f9df135ca873d79, 9f8139c6145cf17d690d6c414d43b4c0bef632fb, 8f42954ad8bf9bdbf574f2c437ad30cb2601f401 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to 538fe5efaa9704ad820ba34b4f9df135ca873d79, 9f8139c6145cf17d690d6c414d43b4c0bef632fb, 8f42954ad8bf9bdbf574f2c437ad30cb2601f401 or 7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to assign driver_data before registering notification handlers. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
Description
A vulnerability in the Linux kernel's vmgenid driver was resolved by changing the order of operations during driver initialization. The issue involved registering notification handlers before setting the driver_data pointer, which could lead to a NULL pointer dereference and kernel panic if a notification arrived early. This affected both device tree and ACPI probe paths. The fix ensures driver_data is assigned before handler registration, preventing the NULL dereference.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98841 (opens in a new tab)
- git.kernel.org/stable/c/538fe5efaa9704ad820ba34b4f9df135ca873d79 (opens in a new tab)
- git.kernel.org/stable/c/7a1e8daeaa466c6aaffa223e1afe9cfeece0dd47 (opens in a new tab)
- git.kernel.org/stable/c/8f42954ad8bf9bdbf574f2c437ad30cb2601f401 (opens in a new tab)
- git.kernel.org/stable/c/9f8139c6145cf17d690d6c414d43b4c0bef632fb (opens in a new tab)