CVE-2026-97910: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-hmww-phv2-5f63
Share
CVSS 7.8
Published
Advisory Summary

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

CVE-2026-97910 at a Glance

CVE Identifier CVE-2026-97910
GHSA Identifier GHSA-hmww-phv2-5f63
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-97910

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-97910, 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: ASoC: sprd: validate compress buffer sizes against fixed allocations sprd_platform_compr_open() allocates the stage 0 IRAM buffer (32K data area) and the stage 1 DDR buffer (2M data area) with fixed sizes, but sprd_platform_compr_copy() derives all copy lengths from the user controlled runtime->fragment_size and the write() count, never comparing them against the physical buffer sizes. The compress core only checks fragment_size * fragments for an u32 overflow in snd_compress_check_input(), so a local user can configure a logical buffer of up to ~4GB via SNDRV_COMPRESS_SET_PARAMS, far exceeding the fixed allocations. A fragment_size larger than the 32K IRAM data area makes the stage 0 copy_from_user() overflow past the IRAM allocation, and a buffer_size larger than the 2M DDR buffer makes the wrapping copy at the end of sprd_platform_compr_copy() write fully user controlled data past the buffer. No SNDRV_PCM_TRIGGER_START is needed, a write() in SETUP state reaches the copy callback directly. Reject parameters that do not fit into the fixed buffers in set_params(), and fix the advertised max fragment size: 128K never fitted into the 32K IRAM buffer. The caps values may have been carried over from the qdsp6 driver, which allocates its buffers according to the advertised maxima, unlike this driver. With 32K as max fragment size the advertised limits are self-consistent: 32K * 64 = 2M equals the DDR buffer size. Discovered by Atuin - Automated Vulnerability Discovery Engine.

References

NVD — CVE-2026-97910 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97910
git.kernel.org/stable/c/1467e3989c... WEB
https://git.kernel.org/stable/c/1467e3989c6edf79d3898c78aa47027f31ee5acb
git.kernel.org/stable/c/2e27144ba4... WEB
https://git.kernel.org/stable/c/2e27144ba4b98bb3eb14aaccd4b088e2e69844e3
git.kernel.org/stable/c/2fada82761... WEB
https://git.kernel.org/stable/c/2fada8276117215407afd1f59de5d2fe22aff01f
git.kernel.org/stable/c/38a9bb5221... WEB
https://git.kernel.org/stable/c/38a9bb5221bcdece5507299f739c6751d8fc16b2
git.kernel.org/stable/c/7a4ce92d15... WEB
https://git.kernel.org/stable/c/7a4ce92d150b9e7ecf1a710a34d8cdeb590d3751
git.kernel.org/stable/c/8064b73997... WEB
https://git.kernel.org/stable/c/8064b73997f137c00a7e2e38295a763f9423928b
git.kernel.org/stable/c/ad796a1bc1... WEB
https://git.kernel.org/stable/c/ad796a1bc1875da2ebb616ea9bc1f2994273fd02
git.kernel.org/stable/c/ff63b0adc4... WEB
https://git.kernel.org/stable/c/ff63b0adc4f6a5b61c8393d204fac44c594c4d39

Frequently Asked Questions

What is CVE-2026-97910?
CVE-2026-97910 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-97910?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-97910?
CVE-2026-97910 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-97910?
CVE-2026-97910 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97910?
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-hmww-phv2-5f63",
  "modified" : "2026-10-03T12:31:20Z",
  "published" : "2026-09-25T12:31:27Z",
  "aliases" : [ "CVE-2026-97910" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: sprd: validate compress buffer sizes against fixed allocations\n\nsprd_platform_compr_open() allocates the stage 0 IRAM buffer (32K data\narea) and the stage 1 DDR buffer (2M data area) with fixed sizes, but\nsprd_platform_compr_copy() derives all copy lengths from the user\ncontrolled runtime->fragment_size and the write() count, never\ncomparing them against the physical buffer sizes. The compress core\nonly checks fragment_size * fragments for an u32 overflow in\nsnd_compress_check_input(), so a local user can configure a logical\nbuffer of up to ~4GB via SNDRV_COMPRESS_SET_PARAMS, far exceeding the\nfixed allocations.\n\nA fragment_size larger than the 32K IRAM data area makes the stage 0\ncopy_from_user() overflow past the IRAM allocation, and a buffer_size\nlarger than the 2M DDR buffer makes the wrapping copy at the end of\nsprd_platform_compr_copy() write fully user controlled data past the\nbuffer. No SNDRV_PCM_TRIGGER_START is needed, a write() in SETUP\nstate reaches the copy callback directly.\n\nReject parameters that do not fit into the fixed buffers in\nset_params(), and fix the advertised max fragment size: 128K never\nfitted into the 32K IRAM buffer. The caps values may have been carried over\nfrom the qdsp6 driver, which allocates its buffers according to the\nadvertised maxima, unlike this driver. With 32K as max fragment size\nthe advertised limits are self-consistent: 32K * 64 = 2M equals the\nDDR buffer size.\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97910"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1467e3989c6edf79d3898c78aa47027f31ee5acb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2e27144ba4b98bb3eb14aaccd4b088e2e69844e3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2fada8276117215407afd1f59de5d2fe22aff01f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/38a9bb5221bcdece5507299f739c6751d8fc16b2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7a4ce92d150b9e7ecf1a710a34d8cdeb590d3751"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8064b73997f137c00a7e2e38295a763f9423928b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ad796a1bc1875da2ebb616ea9bc1f2994273fd02"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ff63b0adc4f6a5b61c8393d204fac44c594c4d39"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:17Z"
  }
}