CVE-2026-98094: Linux kernel · staging: fbtft: make dirty_lock IRQ-safe
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available that changes the locking mechanisms to use IRQ-safe spin locks in the affected functions. Users should update to patched versions of the linux-aws kernel where this issue is resolved. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's staging fbtft driver was resolved involving improper locking mechanisms that could lead to a deadlock. The issue arises because the dirty_lock is accessed in both hard interrupt context and workqueue context without proper IRQ-safe locking, causing a potential IRQ lock inversion and deadlock scenario. This affects specific linux-aws kernel versions.
References
- ubuntu.com/security/CVE-2026-98094 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98094 (opens in a new tab)
- git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7 (opens in a new tab)
- git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00 (opens in a new tab)
- git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c (opens in a new tab)
- git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-98094 (opens in a new tab)
- git.kernel.org/stable/c/0843298b159599ee7bc6d14800efdb4bc7349706 (opens in a new tab)
- git.kernel.org/stable/c/10cc145b873670438d3b105133dffdae70822db6 (opens in a new tab)
- git.kernel.org/stable/c/a323066337ed85c38decfc7f6bbf42f27605dff1 (opens in a new tab)
- git.kernel.org/stable/c/f2451e18826eb6a33ea51419f39bdd2eb99fa1ea (opens in a new tab)