{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-98094 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98094 is a medium-severity vulnerability in Linux kernel, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98094 and fix it if it is affected.\n\nWhat it is: CVE-2026-98094 is a medium-severity vulnerability in Linux kernel, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98094 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98094/ (Markdown: https://insights.sbomify.com/CVE-2026-98094/index.md)","id":"CVE-2026-98094","markdown":"https://insights.sbomify.com/CVE-2026-98094/index.md","name":"CVE-2026-98094","record":{"aliases":["AZL-104595","BELL-CVE-2026-98094","DEBIAN-CVE-2026-98094","GHSA-5wg8-22v7-6q2c","UBUNTU-CVE-2026-98094"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A race condition in the fbtft staging driver can cause a deadlock when printing logs, leading to a system denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-667","name":"Improper Locking"}],"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  (\u0026par-\u003edirty_lock){+.+.}-{2:2}\n\n  CPU0                    CPU1\n  ----                    ----\n  lock(\u0026par-\u003edirty_lock);\n                         local_irq_disable();\n                         lock(console_owner);\n                         lock(\u0026par-\u003edirty_lock);\n  \u003cInterrupt\u003e\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"staging: fbtft: make dirty_lock IRQ-safe","id":"CVE-2026-98094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header().","id":"CVE-2026-98095"},"packages":[],"prev":{"headline":"ASoC: fsl_micfil: balance mclk enable/disable","id":"CVE-2026-98093"},"products":["Linux"],"published":"2026-09-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the fbtft staging driver can cause a deadlock when printing logs, leading to a system denial of service.","url":"https://insights.sbomify.com/CVE-2026-98094/"}