VulnerabilityPublished 25 Sep 2026Updated 19 Oct 2026

CVE-2026-98094: Linux kernel · staging: fbtft: make dirty_lock IRQ-safe

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f576944a59f31bcffff121117ebf452c5dd162b7 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · 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.
Patch: Available – fixed in f576944a59f31bcffff121117ebf452c5dd162b7, f2451e18826eb6a33ea51419f39bdd2eb99fa1ea, f0c869df2c33793c8828acaab3e4a5e0176f9f00 +5

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ c296d5f9957c03994a699d6739c27d4581a9f6c7, < f576944a59f31bcffff121117ebf452c5dd162b7	Fixed in f576944a59f31bcffff121117ebf452c5dd162b7
LinuxLinux	Affected ≥ c296d5f9957c03994a699d6739c27d4581a9f6c7, < f2451e18826eb6a33ea51419f39bdd2eb99fa1ea	Fixed in f2451e18826eb6a33ea51419f39bdd2eb99fa1ea
LinuxLinux	Affected ≥ c296d5f9957c03994a699d6739c27d4581a9f6c7, < f0c869df2c33793c8828acaab3e4a5e0176f9f00	Fixed in f0c869df2c33793c8828acaab3e4a5e0176f9f00
LinuxLinux	Affected ≥ c296d5f9957c03994a699d6739c27d4581a9f6c7, < dcb48fde8003492256dee45815144aa5ed26ce7c	Fixed in dcb48fde8003492256dee45815144aa5ed26ce7c
LinuxLinux	Affected ≥ c296d5f9957c03994a699d6739c27d4581a9f6c7, < a323066337ed85c38decfc7f6bbf42f27605dff1	Fixed in a323066337ed85c38decfc7f6bbf42f27605dff1
LinuxLinux	Affected ≥ c296d5f9957c03994a699d6739c27d4581a9f6c7, < 0843298b159599ee7bc6d14800efdb4bc7349706	Fixed in 0843298b159599ee7bc6d14800efdb4bc7349706

AI-suggested

A fix is available and has been applied in the Linux kernel source as indicated by the fixed commit hashes. Users and administrators should update to a Linux kernel version that includes these fixes. No additional mitigation steps are required beyond applying the official patch.

Description

CVE-2026-98094 is a Linux kernel vulnerability in the staging fbtft driver where the dirty_lock is not IRQ-safe, leading to a potential deadlock due to lock inversion between dirty_lock and console_owner. This occurs because fbtft_mkdirty() can be called in hardirq context while dirty_lock is also taken in workqueue context with interrupts enabled. The issue was observed on RK3566 systems with CONFIG_PROVE_LOCKING enabled and has been fixed by making dirty_lock IRQ-safe using spin_lock_irqsave() and spin_lock_irq().

Impact

The vulnerability can cause a deadlock in the Linux kernel on affected systems, potentially leading to system hangs or instability when the fbtft driver is used. This impacts systems using the affected driver, such as RK3566-based devices, under certain conditions involving concurrent access to dirty_lock in interrupt and workqueue contexts.

Summary

The vulnerability in the Linux kernel's staging fbtft driver involves improper locking of dirty_lock, which is accessed both in hardirq context via fbtft_mkdirty() and in workqueue context via fbtft_deferred_io(). This leads to a possible IRQ lock inversion and deadlock when a hardirq interrupts a CPU holding dirty_lock and attempts to acquire it again through the console rendering path. Lockdep reports confirm this deadlock scenario. The fix involves using spin_lock_irqsave() for fbtft_mkdirty() and spin_lock_irq() for fbtft_deferred_io() to ensure IRQ safety while keeping IRQ-off regions short.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 12:43 UTC

Technical details

References

Community reviews

Related threats