{"api_version":"1","generated_at":"2026-09-26T06:40:12+00:00","cve":"CVE-2026-98094","urls":{"html":"https://cve.report/CVE-2026-98094","api":"https://cve.report/api/cve/CVE-2026-98094.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98094","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98094"},"summary":{"title":"staging: fbtft: make dirty_lock IRQ-safe","description":"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_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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:39","updated_at":"2026-09-25 11:17:39"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7","name":"https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00","name":"https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7","name":"https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c","name":"https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98094","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98094","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c296d5f9957c03994a699d6739c27d4581a9f6c7 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c296d5f9957c03994a699d6739c27d4581a9f6c7 f0c869df2c33793c8828acaab3e4a5e0176f9f00 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c296d5f9957c03994a699d6739c27d4581a9f6c7 dcb48fde8003492256dee45815144aa5ed26ce7c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c296d5f9957c03994a699d6739c27d4581a9f6c7 f576944a59f31bcffff121117ebf452c5dd162b7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/staging/fbtft/fbtft-core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7","status":"affected","version":"c296d5f9957c03994a699d6739c27d4581a9f6c7","versionType":"git"},{"lessThan":"f0c869df2c33793c8828acaab3e4a5e0176f9f00","status":"affected","version":"c296d5f9957c03994a699d6739c27d4581a9f6c7","versionType":"git"},{"lessThan":"dcb48fde8003492256dee45815144aa5ed26ce7c","status":"affected","version":"c296d5f9957c03994a699d6739c27d4581a9f6c7","versionType":"git"},{"lessThan":"f576944a59f31bcffff121117ebf452c5dd162b7","status":"affected","version":"c296d5f9957c03994a699d6739c27d4581a9f6c7","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/staging/fbtft/fbtft-core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.0"},{"lessThan":"4.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"4.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"4.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"4.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"4.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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_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."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:24:25.889Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7"},{"url":"https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00"},{"url":"https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c"},{"url":"https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7"}],"title":"staging: fbtft: make dirty_lock IRQ-safe","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98094","datePublished":"2026-09-25T10:24:25.889Z","dateReserved":"2026-09-25T10:19:56.076Z","dateUpdated":"2026-09-25T10:24:25.889Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:39","lastModifiedDate":"2026-09-25 11:17:39","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98094","Ordinal":"1","Title":"staging: fbtft: make dirty_lock IRQ-safe","CVE":"CVE-2026-98094","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98094","Ordinal":"1","NoteData":"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_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.","Type":"Description","Title":"staging: fbtft: make dirty_lock IRQ-safe"}]}}}