CVE-2026-98094

staging: fbtft: make dirty_lock IRQ-safe

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.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.095% likely to be exploited in the next 30 days, higher than 0.608% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding 0843298b159599ee7bc6d14800efdb4bc7349706 (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding a323066337ed85c38decfc7f6bbf42f27605dff1 (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding f2451e18826eb6a33ea51419f39bdd2eb99fa1ea (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding 10cc145b873670438d3b105133dffdae70822db6 (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7 (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding f0c869df2c33793c8828acaab3e4a5e0176f9f00 (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding dcb48fde8003492256dee45815144aa5ed26ce7c (affected)
  • c296d5f9957c03994a699d6739c27d4581a9f6c7 up to but excluding f576944a59f31bcffff121117ebf452c5dd162b7 (affected)
LinuxLinux
  • Default status: affected
  • 4.0 (affected)
  • 0 up to but excluding 4.0 (unaffected)
  • 5.10.271 up to and including 5.10.* (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References