Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98094staging: 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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-98094, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 0843298b159599ee7bc6d14800efdb4bc7349706
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < a323066337ed85c38decfc7f6bbf42f27605dff1
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < f2451e18826eb6a33ea51419f39bdd2eb99fa1ea
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 10cc145b873670438d3b105133dffdae70822db6
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < f0c869df2c33793c8828acaab3e4a5e0176f9f00
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < dcb48fde8003492256dee45815144aa5ed26ce7c
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < f576944a59f31bcffff121117ebf452c5dd162b7
  • Linux · Linux

    • affected 4.0
    • unaffected < 4.0
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98094 badge
[![CVE-2026-98094](https://cveledger.app/badge/CVE-2026-98094.svg)](https://cveledger.app/cve/CVE-2026-98094)

Record last updated .