{"id":"CVE-2026-98094","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: fbtft: make dirty_lock IRQ-safe\n\nfbtft_mkdirty() can be reached from the fbcon rendering path while\nprocessing printk() in hardirq context","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: fbtft: make dirty_lock IRQ-safe\n\nfbtft_mkdirty() can be reached from the fbcon rendering path while\nprocessing printk() in hardirq context. Meanwhile, dirty_lo…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= c296d5f9957c03994a699d6739c27d4581a9f6c7 < 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7","Linux >= c296d5f9957c03994a699d6739c27d4581a9f6c7 < f0c869df2c33793c8828acaab3e4a5e0176f9f00","Linux >= c296d5f9957c03994a699d6739c27d4581a9f6c7 < dcb48fde8003492256dee45815144aa5ed26ce7c","Linux >= c296d5f9957c03994a699d6739c27d4581a9f6c7 < f576944a59f31bcffff121117ebf452c5dd162b7","Linux 4.0"],"published":"2026-09-25","updated":"2026-09-25","sourceUpdated":"2026-09-25T11:17:39.133","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-98094","references":[{"url":"https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-25T11:06:38.831Z","slug":"CVE-2026-98094","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nstaging: fbtft: make dirty_lock IRQ-safe\n\nfbtft_mkdirty() can be reached from the fbcon rendering path while\nprocessing printk() in hardirq context. Meanwhile, dirty_lock is also\ntaken by fbtft_deferred_io() in workqueue context with local interrupts\nenabled.\n\nLockdep reports a possible IRQ lock inversion involving dirty_lock and\nconsole_owner. A hardirq can interrupt a CPU holding dirty_lock and\nenter the console rendering path, which can attempt to acquire\ndirty_lock again.\n\nThe following lockdep report was observed on an RK3566 system with\nCONFIG_PROVE_LOCKING enabled:\n\n  WARNING: possible irq lock inversion dependency detected\n  swapper/2/0 just changed the state of lock:\n  (console_owner){-...}-{0:0}\n  but this lock took another, HARDIRQ-unsafe lock in the past:\n  (&par->dirty_lock){+.+.}-{2:2}\n\n  CPU0                    CPU1\n  ----                    ----\n  lock(&par->dirty_lock);\n                         local_irq_disable();\n                         lock(console_owner);\n                         lock(&par->dirty_lock);\n  <Interrupt>\n    lock(console_owner);\n\n  *** DEADLOCK ***\n\nUse spin_lock_irqsave() for fbtft_mkdirty() and spin_lock_irq() for\nfbtft_deferred_io(). They only access the dirty line range, so the\nIRQ-off regions remain short.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}