CVE-2026-98198: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-vr2q-55hv-76j4
Share
Published
Advisory Summary

CVE-2026-98198 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-98198 at a Glance

CVE Identifier CVE-2026-98198
GHSA Identifier GHSA-vr2q-55hv-76j4
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-98198

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-98198, 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: hwmon: (pwm-fan) Stop RPM timer before freeing tach data sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated. Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data. With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions. With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released. Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.

References

NVD — CVE-2026-98198 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98198
git.kernel.org/stable/c/1e824fdb14... WEB
https://git.kernel.org/stable/c/1e824fdb14a187ce56697e803b02b1e86243a755
git.kernel.org/stable/c/26d5ff7976... WEB
https://git.kernel.org/stable/c/26d5ff79768548efb1e604bb6e8697c101e06269
git.kernel.org/stable/c/a5ce3fe533... WEB
https://git.kernel.org/stable/c/a5ce3fe5335a24d0220958c6866830a6d5fa1cc0
git.kernel.org/stable/c/b48339b0a5... WEB
https://git.kernel.org/stable/c/b48339b0a577783e4590a69e4cd2f2760ce33154

Frequently Asked Questions

What is CVE-2026-98198?
CVE-2026-98198 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-98198?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98198?
CVE-2026-98198 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98198?
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-vr2q-55hv-76j4",
  "modified" : "2026-10-06T09:31:30Z",
  "published" : "2026-10-06T09:31:29Z",
  "aliases" : [ "CVE-2026-98198" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (pwm-fan) Stop RPM timer before freeing tach data\n\nsample_timer() rearms the RPM timer and accesses the devm-managed\nctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action\nwhich stops the timer is registered before those arrays are allocated.\n\nSince devres releases entries in reverse order, driver detach can free\nthe arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry\nin that window accesses the freed tach data.\n\nWith a KASAN kernel, a test-only kprobe delayed entry to\npwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs\nreported three four-byte reads and two four-byte writes in sample_timer()\nafter its backing devm allocations had been freed. The helper did not\ninvoke the timer callback, cleanup actions or free functions.\n\nWith the fix, three matching unbind runs completed without KASAN, BUG,\nWARNING, Oops or panic. Instrumentation confirmed that timer retirement\ncompleted before the first timer backing allocation was released.\n\nSplit timer retirement from the power cleanup and register its devres\naction after the timer backing data and IRQ actions are installed. This\npreserves the early power rollback action while ensuring the timer is\nretired before its backing data is released. Use timer_shutdown_sync()\nbecause the callback can rearm itself.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98198"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1e824fdb14a187ce56697e803b02b1e86243a755"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/26d5ff79768548efb1e604bb6e8697c101e06269"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a5ce3fe5335a24d0220958c6866830a6d5fa1cc0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b48339b0a577783e4590a69e4cd2f2760ce33154"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:05Z"
  }
}