CVE-2026-98314: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-f958-2rwj-98rc
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98314
GHSA Identifier GHSA-f958-2rwj-98rc
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-98314

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-98314, 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: ALSA: pcm: set timer->private_data before registering the PCM timer snd_pcm_timer_init() calls snd_device_register() to link the new struct snd_timer into the global timer list while it still carries hw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop), and only afterwards sets timer->private_data = substream. Once the timer is on the list under register_mutex, a concurrent reader can already reach it through the same mutex and invoke these callbacks. /proc/asound/timers does this via c_resolution(), and snd_timer_open()+snd_timer_start() reach start()/stop() the same way. All three dereference timer->private_data, which for this brief window is NULL, giving a NULL-pointer dereference: substream = timer->private_data; return substream->runtime ? ... // substream is NULL Move the private_data/private_free assignment before snd_device_register() so the timer is never visible on the list without its private_data set. On the snd_device_register() failure path, private_free() (snd_pcm_timer_free()) can now run, but it only does substream->timer = NULL, which is already NULL at that point since substream->timer is set to the new timer just once, after a successful registration -- so the failure path stays safe.

References

NVD — CVE-2026-98314 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98314
git.kernel.org/stable/c/0b349249d5... WEB
https://git.kernel.org/stable/c/0b349249d572633d7c8cdeb917623d1676a2b7c3
git.kernel.org/stable/c/1e713f9bb2... WEB
https://git.kernel.org/stable/c/1e713f9bb2ac583521f06b0eb4e22440b1e3d078
git.kernel.org/stable/c/27f167e117... WEB
https://git.kernel.org/stable/c/27f167e117eca310661fbcbacb352ea08face067
git.kernel.org/stable/c/555d168bd9... WEB
https://git.kernel.org/stable/c/555d168bd98daa46daccc68c908201388c834293
git.kernel.org/stable/c/686c7a6af1... WEB
https://git.kernel.org/stable/c/686c7a6af1eea8d2a919303e4c6bbec3de79dbdc
git.kernel.org/stable/c/8c869d5cf5... WEB
https://git.kernel.org/stable/c/8c869d5cf5affb20994bdbb60e7d46d65c91b55f
git.kernel.org/stable/c/d63f5a9f81... WEB
https://git.kernel.org/stable/c/d63f5a9f8121fb43c798056d7dd34c58f47185d7
git.kernel.org/stable/c/e1eee8f166... WEB
https://git.kernel.org/stable/c/e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd

Frequently Asked Questions

What is CVE-2026-98314?
CVE-2026-98314 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-98314?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98314?
CVE-2026-98314 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98314?
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-f958-2rwj-98rc",
  "modified" : "2026-10-06T09:31:34Z",
  "published" : "2026-10-06T09:31:34Z",
  "aliases" : [ "CVE-2026-98314" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: pcm: set timer->private_data before registering the PCM timer\n\nsnd_pcm_timer_init() calls snd_device_register() to link the new\nstruct snd_timer into the global timer list while it still carries\nhw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop),\nand only afterwards sets timer->private_data = substream.\n\nOnce the timer is on the list under register_mutex, a concurrent\nreader can already reach it through the same mutex and invoke these\ncallbacks. /proc/asound/timers does this via c_resolution(), and\nsnd_timer_open()+snd_timer_start() reach start()/stop() the same way.\nAll three dereference timer->private_data, which for this brief\nwindow is NULL, giving a NULL-pointer dereference:\n\n  substream = timer->private_data;\n  return substream->runtime ? ...   // substream is NULL\n\nMove the private_data/private_free assignment before\nsnd_device_register() so the timer is never visible on the list\nwithout its private_data set. On the snd_device_register() failure\npath, private_free() (snd_pcm_timer_free()) can now run, but it only\ndoes substream->timer = NULL, which is already NULL at that point\nsince substream->timer is set to the new timer just once, after a\nsuccessful registration -- so the failure path stays safe.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98314"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0b349249d572633d7c8cdeb917623d1676a2b7c3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1e713f9bb2ac583521f06b0eb4e22440b1e3d078"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/27f167e117eca310661fbcbacb352ea08face067"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/555d168bd98daa46daccc68c908201388c834293"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/686c7a6af1eea8d2a919303e4c6bbec3de79dbdc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8c869d5cf5affb20994bdbb60e7d46d65c91b55f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d63f5a9f8121fb43c798056d7dd34c58f47185d7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:23Z"
  }
}