Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-98094: staging: fbtft: make dirty_lock IRQ-safe

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0843298b159599ee7bc6d14800efdb4bc7349706, 10cc145b873670438d3b105133dffdae70822db6, 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0843298b159599ee7bc6d14800efdb4bc7349706, 10cc145b873670438d3b105133dffdae70822db6, 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Sep 25, 2026
Updated
Oct 23, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98094

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.0affected
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before 0843298b159599ee7bc6d14800efdb4bc7349706affected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before a323066337ed85c38decfc7f6bbf42f27605dff1affected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before f2451e18826eb6a33ea51419f39bdd2eb99fa1eaaffected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before 10cc145b873670438d3b105133dffdae70822db6affected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before 2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7affected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before f0c869df2c33793c8828acaab3e4a5e0176f9f00affected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before dcb48fde8003492256dee45815144aa5ed26ce7caffected · git
    • c296d5f9957c03994a699d6739c27d4581a9f6c7 and later · before f576944a59f31bcffff121117ebf452c5dd162b7affected · git
    • before 4.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.7-17.2.7-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-98092Sep 25, 2026 · ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close()
    22Monitor
  • ← EarlierCVE-2026-98093Sep 25, 2026 · ASoC: fsl_micfil: balance mclk enable/disable
    31Monitor
  • Later →CVE-2026-98095Sep 25, 2026 · af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header().
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0843298b159599ee7bc6d14800efdb4bc7349706Vendor (CNA)
Linux Linux10cc145b873670438d3b105133dffdae70822db6Vendor (CNA)
Linux Linux2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7Vendor (CNA)
Linux Linuxa323066337ed85c38decfc7f6bbf42f27605dff1Vendor (CNA)
Linux Linuxdcb48fde8003492256dee45815144aa5ed26ce7cVendor (CNA)
Linux Linuxf0c869df2c33793c8828acaab3e4a5e0176f9f00Vendor (CNA)
Linux Linuxf2451e18826eb6a33ea51419f39bdd2eb99fa1eaVendor (CNA)
Linux Linuxf576944a59f31bcffff121117ebf452c5dd162b7Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. CVSS— → 5.5
  2. Severity— → medium
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records