CVE-2026-80569: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-3268-6g62-7794
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-80569
GHSA Identifier GHSA-3268-6g62-7794
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-80569

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-80569, 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: synaptics-rmi4 - bound the F54 report size to the allocated buffer rmi_f54_work() reads a diagnostics report from the device into f54->report_data, sizing the transfer with rmi_f54_get_report_size(): report_size = rmi_f54_get_report_size(f54); ... for (i = 0; i < report_size; i += F54_REPORT_DATA_SIZE) { int size = min(F54_REPORT_DATA_SIZE, report_size - i); ... rmi_read_block(.., f54->report_data + i, size); } report_data is allocated once at probe from F54's own electrode counts (array3_size(f54->num_tx_electrodes, f54->num_rx_electrodes, sizeof(u16))), but rmi_f54_get_report_size() computes the size from drv_data->num_*_electrodes when those are set, i.e. from the F55 function's electrode counts. Both counts come straight from device queries (F54 and F55 each report up to 255 electrodes) and nothing constrains the F55 counts to the F54 ones. A malicious or malfunctioning RMI4 device that reports larger F55 electrode counts than its F54 counts makes report_size exceed the allocation, so the read loop writes past report_data (and the V4L2 dequeue memcpy() then reads past it). On conforming hardware the F55 configured electrodes are a subset of the F54 physical electrodes, so report_size never exceeds the buffer and well-behaved devices are unaffected. Record the allocation size and reject a report that does not fit, mirroring the existing zero-size check.

References

NVD — CVE-2026-80569 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80569
git.kernel.org/stable/c/12be3c6ca9... WEB
https://git.kernel.org/stable/c/12be3c6ca9589afd6ade41a59c761866e526634d
git.kernel.org/stable/c/42eaf0e6f7... WEB
https://git.kernel.org/stable/c/42eaf0e6f79c487f419737314cf0760f7331d368
git.kernel.org/stable/c/49c5adc2b7... WEB
https://git.kernel.org/stable/c/49c5adc2b7d6e43c5cf033e1c86fdb9c16ababb1
git.kernel.org/stable/c/6b06aab79f... WEB
https://git.kernel.org/stable/c/6b06aab79ff166d5781ce792d91acc2e58b1770b
git.kernel.org/stable/c/6b3bdd44d4... WEB
https://git.kernel.org/stable/c/6b3bdd44d4cd7d5e35de1d0f06d4930f3cecd403
git.kernel.org/stable/c/b2f596f00d... WEB
https://git.kernel.org/stable/c/b2f596f00d27703ce09167201ba57f55be8d2f9a
git.kernel.org/stable/c/b3932101c9... WEB
https://git.kernel.org/stable/c/b3932101c9c457148038392bc977f9b31e125a86
git.kernel.org/stable/c/b7b9a8b1c3... WEB
https://git.kernel.org/stable/c/b7b9a8b1c303b62371698e396654d6724c79cb74

Frequently Asked Questions

What is CVE-2026-80569?
CVE-2026-80569 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-80569?
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-80569?
CVE-2026-80569 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-80569?
CVE-2026-80569 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80569?
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-3268-6g62-7794",
  "modified" : "2026-08-27T06:31:32Z",
  "published" : "2026-08-27T06:31:32Z",
  "aliases" : [ "CVE-2026-80569" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nInput: synaptics-rmi4 - bound the F54 report size to the allocated buffer\n\nrmi_f54_work() reads a diagnostics report from the device into\nf54->report_data, sizing the transfer with rmi_f54_get_report_size():\n\n\treport_size = rmi_f54_get_report_size(f54);\n\t...\n\tfor (i = 0; i < report_size; i += F54_REPORT_DATA_SIZE) {\n\t\tint size = min(F54_REPORT_DATA_SIZE, report_size - i);\n\t\t...\n\t\trmi_read_block(.., f54->report_data + i, size);\n\t}\n\nreport_data is allocated once at probe from F54's own electrode counts\n(array3_size(f54->num_tx_electrodes, f54->num_rx_electrodes, sizeof(u16))),\nbut rmi_f54_get_report_size() computes the size from\ndrv_data->num_*_electrodes when those are set, i.e. from the F55\nfunction's electrode counts. Both counts come straight from device\nqueries (F54 and F55 each report up to 255 electrodes) and nothing\nconstrains the F55 counts to the F54 ones.\n\nA malicious or malfunctioning RMI4 device that reports larger F55\nelectrode counts than its F54 counts makes report_size exceed the\nallocation, so the read loop writes past report_data (and the V4L2\ndequeue memcpy() then reads past it). On conforming hardware the F55\nconfigured electrodes are a subset of the F54 physical electrodes, so\nreport_size never exceeds the buffer and well-behaved devices are\nunaffected.\n\nRecord the allocation size and reject a report that does not fit,\nmirroring the existing zero-size check.",
  "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-80569"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/12be3c6ca9589afd6ade41a59c761866e526634d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/42eaf0e6f79c487f419737314cf0760f7331d368"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/49c5adc2b7d6e43c5cf033e1c86fdb9c16ababb1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6b06aab79ff166d5781ce792d91acc2e58b1770b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6b3bdd44d4cd7d5e35de1d0f06d4930f3cecd403"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b2f596f00d27703ce09167201ba57f55be8d2f9a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b3932101c9c457148038392bc977f9b31e125a86"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b7b9a8b1c303b62371698e396654d6724c79cb74"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-26T15:17:12Z"
  }
}