CVE-2026-80575: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-6c2r-6hqv-3xph
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-80575
GHSA Identifier GHSA-6c2r-6hqv-3xph
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-80575

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-80575, 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: Input: cs40l50-vibra - validate custom data from user space cs40l50_add() copies the custom data of an FF_PERIODIC/FF_CUSTOM effect straight from the ff_effect the user passed to EVIOCSFF, without requiring it to hold anything: work_data.custom_data = memdup_array_user(periodic->custom_data, periodic->custom_len, sizeof(s16)); work_data.custom_len = periodic->custom_len; The driver then reads two words out of that buffer: custom_data[0] as the waveform bank in cs40l50_effect_bank_set(), and custom_data[1] as the index within the bank in cs40l50_effect_index_set(). Neither read is covered by a length check, and custom_len is fully user controlled: - custom_len == 0 makes memdup_array_user() call memdup_user() with a length of zero, which returns ZERO_SIZE_PTR rather than an error, so custom_data[0] dereferences it. - custom_len == 1 allocates two bytes. A bank of ROM or RAM keeps effect->type out of the OWT case, and custom_data[1] is then read one word past the allocation. The bank value itself is also mishandled. It is masked with CS40L50_CUSTOM_DATA_MASK (0xffff) but stored in an s16, so a custom_data[0] of 0x8000 or above wraps to a negative value that passes the "bank_type >= CS40L50_WVFRM_BANK_NUM" test. cs40l50_effect_index_set() indexes vib->dsp.banks[] with it before the switch statement's default case gets a chance to reject it: base_index = vib->dsp.banks[effect->type].base_index; max_index = vib->dsp.banks[effect->type].max_index; Require the two words the driver reads to be present, and hold the masked bank in a u32 so the existing upper-bound test covers the whole range. The da7280 haptic driver already range checks custom_len this way.

References

NVD — CVE-2026-80575 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80575
git.kernel.org/stable/c/3855b6a11f... WEB
https://git.kernel.org/stable/c/3855b6a11f8a7aceb8181cc08c99afef58517006
git.kernel.org/stable/c/52a818c586... WEB
https://git.kernel.org/stable/c/52a818c586ae2c36b7324bfaefb547f5e866a8ae
git.kernel.org/stable/c/7d5c576cb1... WEB
https://git.kernel.org/stable/c/7d5c576cb1c86047b1fcb1aa9532e17fc5e46c1d
git.kernel.org/stable/c/d38554602a... WEB
https://git.kernel.org/stable/c/d38554602a0b04e85fad28ce72c7500cf50d419b

Frequently Asked Questions

What is CVE-2026-80575?
CVE-2026-80575 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-80575?
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-80575?
CVE-2026-80575 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-80575?
CVE-2026-80575 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80575?
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-6c2r-6hqv-3xph",
  "modified" : "2026-08-27T06:31:32Z",
  "published" : "2026-08-27T06:31:32Z",
  "aliases" : [ "CVE-2026-80575" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nInput: cs40l50-vibra - validate custom data from user space\n\ncs40l50_add() copies the custom data of an FF_PERIODIC/FF_CUSTOM effect\nstraight from the ff_effect the user passed to EVIOCSFF, without\nrequiring it to hold anything:\n\n    work_data.custom_data = memdup_array_user(periodic->custom_data,\n                                              periodic->custom_len,\n                                              sizeof(s16));\n    work_data.custom_len = periodic->custom_len;\n\nThe driver then reads two words out of that buffer: custom_data[0] as the\nwaveform bank in cs40l50_effect_bank_set(), and custom_data[1] as the\nindex within the bank in cs40l50_effect_index_set().  Neither read is\ncovered by a length check, and custom_len is fully user controlled:\n\n  - custom_len == 0 makes memdup_array_user() call memdup_user() with a\n    length of zero, which returns ZERO_SIZE_PTR rather than an error, so\n    custom_data[0] dereferences it.\n\n  - custom_len == 1 allocates two bytes.  A bank of ROM or RAM keeps\n    effect->type out of the OWT case, and custom_data[1] is then read one\n    word past the allocation.\n\nThe bank value itself is also mishandled.  It is masked with\nCS40L50_CUSTOM_DATA_MASK (0xffff) but stored in an s16, so a\ncustom_data[0] of 0x8000 or above wraps to a negative value that passes\nthe \"bank_type >= CS40L50_WVFRM_BANK_NUM\" test.\ncs40l50_effect_index_set() indexes vib->dsp.banks[] with it before the\nswitch statement's default case gets a chance to reject it:\n\n    base_index = vib->dsp.banks[effect->type].base_index;\n    max_index = vib->dsp.banks[effect->type].max_index;\n\nRequire the two words the driver reads to be present, and hold the masked\nbank in a u32 so the existing upper-bound test covers the whole range.\nThe da7280 haptic driver already range checks custom_len this way.",
  "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-80575"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3855b6a11f8a7aceb8181cc08c99afef58517006"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/52a818c586ae2c36b7324bfaefb547f5e866a8ae"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d5c576cb1c86047b1fcb1aa9532e17fc5e46c1d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d38554602a0b04e85fad28ce72c7500cf50d419b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-26T15:17:13Z"
  }
}