{"id":29249,"date":"2026-09-25T20:32:15","date_gmt":"2026-09-25T12:32:15","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98094"},"modified":"2026-09-25T20:32:15","modified_gmt":"2026-09-25T12:32:15","slug":"cve-2026-98094","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98094","title":{"rendered":"CVE-2026-98094 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: fbtft: make"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>staging: fbtft: make dirty_lock IRQ-safe<\/p>\n<p>fbtft_mkdirty() can be reached from the fbcon rendering path while<br \/>\nprocessing printk() in hardirq context. Meanwhile, dirty_lock is also<br \/>\ntaken by fbtft_deferred_io() in workqueue context with local interrupts<br \/>\nenabled.<\/p>\n<p>Lockdep reports a possible IRQ lock inversion involving dirty_lock and<br \/>\nconsole_owner. A hardirq can interrupt a CPU holding dirty_lock and<br \/>\nenter the console rendering path, which can attempt to acquire<br \/>\ndirty_lock again.<\/p>\n<p>The following lockdep report was observed on an RK3566 system with<br \/>\nCONFIG_PROVE_LOCKING enabled:<\/p>\n<p>  WARNING: possible irq lock inversion dependency detected<br \/>\n  swapper\/2\/0 just changed the state of lock:<br \/>\n  (console_owner){-&#8230;}-{0:0}<br \/>\n  but this lock took another, HARDIRQ-unsafe lock in the past:<br \/>\n  (&amp;par-&gt;dirty_lock){+.+.}-{2:2}<\/p>\n<p>  CPU0                    CPU1<br \/>\n  &#8212;-                    &#8212;-<br \/>\n  lock(&amp;par-&gt;dirty_lock);<br \/>\n                         local_irq_disable();<br \/>\n                         lock(console_owner);<br \/>\n                         lock(&amp;par-&gt;dirty_lock);<\/p>\n<p>    lock(console_owner);<\/p>\n<p>  *** DEADLOCK ***<\/p>\n<p>Use spin_lock_irqsave() for fbtft_mkdirty() and spin_lock_irq() for<br \/>\nfbtft_deferred_io(). They only access the dirty line range, so the<br \/>\nIRQ-off regions remain short.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>staging: fbtft: make dirty_lock IRQ-safe<\/p>\n<p>fbtft_mkdirty() can be reached from the fbcon rendering path while<br \/>\nprocessing printk() in<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-29249","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/29249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=29249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=29249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=29249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}