CVE-2026-98094: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-5wg8-22v7-6q2c
Share
Published
Advisory Summary

CVE-2026-98094 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98094 at a Glance

CVE Identifier CVE-2026-98094
GHSA Identifier GHSA-5wg8-22v7-6q2c
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98094

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98094, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-98094 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98094
git.kernel.org/stable/c/0843298b15... WEB
https://git.kernel.org/stable/c/0843298b159599ee7bc6d14800efdb4bc7349706
git.kernel.org/stable/c/10cc145b87... WEB
https://git.kernel.org/stable/c/10cc145b873670438d3b105133dffdae70822db6
git.kernel.org/stable/c/2a609e29ef... WEB
https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7
git.kernel.org/stable/c/a323066337... WEB
https://git.kernel.org/stable/c/a323066337ed85c38decfc7f6bbf42f27605dff1
git.kernel.org/stable/c/dcb48fde80... WEB
https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c
git.kernel.org/stable/c/f0c869df2c... WEB
https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00
git.kernel.org/stable/c/f2451e1882... WEB
https://git.kernel.org/stable/c/f2451e18826eb6a33ea51419f39bdd2eb99fa1ea
git.kernel.org/stable/c/f576944a59... WEB
https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7

Frequently Asked Questions

What is CVE-2026-98094?
CVE-2026-98094 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98094?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98094?
CVE-2026-98094 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98094?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5wg8-22v7-6q2c",
  "modified" : "2026-10-03T12:31:27Z",
  "published" : "2026-09-25T12:31:36Z",
  "aliases" : [ "CVE-2026-98094" ],
  "details" : "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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98094"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0843298b159599ee7bc6d14800efdb4bc7349706"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/10cc145b873670438d3b105133dffdae70822db6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2a609e29efbba79f9abd68c4ec8a2bd7ecf291e7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a323066337ed85c38decfc7f6bbf42f27605dff1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dcb48fde8003492256dee45815144aa5ed26ce7c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f0c869df2c33793c8828acaab3e4a5e0176f9f00"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f2451e18826eb6a33ea51419f39bdd2eb99fa1ea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f576944a59f31bcffff121117ebf452c5dd162b7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:39Z"
  }
}