CVE-2026-80761: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-xhh3-4cvw-88vv
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80761
GHSA Identifier GHSA-xhh3-4cvw-88vv
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-80761

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-80761, 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: Bluetooth: ISO: zero the sockaddr before returning it in getname iso_sock_getname() fills a struct sockaddr_iso in place and returns its size without clearing it first, so bytes it does not write are copied to user space from the kernel stack. The getsockname(2) and getpeername(2) paths both run through do_getsockname(), which hands getname() an uninitialized sockaddr_storage on the stack and copies back up to the number of bytes getname() returns, so the driver has to initialize every byte it accounts for. Two ranges are left uninitialized: - struct sockaddr_iso is 10 bytes but only 9 are written (family, iso_bdaddr, iso_bdaddr_type), leaking the trailing pad byte on every call. - for a broadcast peer (BIS_LINK or PA_LINK) the returned length grows by sizeof(struct sockaddr_iso_bc), but only bc_sid, bc_num_bis and bc_bis are filled; bc_bdaddr and bc_bdaddr_type, the first 7 bytes of that structure, are never written. An unprivileged process can open a BTPROTO_ISO socket and reach the pad leak with getsockname(); the broadcast leak needs an established BIS/PA connection. l2cap and rfcomm already memset their sockaddr in getname for the same reason; do the same here.

References

NVD — CVE-2026-80761 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80761
git.kernel.org/stable/c/190b719b78... WEB
https://git.kernel.org/stable/c/190b719b787eb4ca6c25b12fab224806f9108b06
git.kernel.org/stable/c/1f6d1f2611... WEB
https://git.kernel.org/stable/c/1f6d1f2611af0eb36b133a41d29ffd2cc2601615
git.kernel.org/stable/c/884cf2cc95... WEB
https://git.kernel.org/stable/c/884cf2cc957da7ac178a0e6c6c69ddfec0481cc8
git.kernel.org/stable/c/9069be87c6... WEB
https://git.kernel.org/stable/c/9069be87c67f290783b332c4284e09fb89cb9ea7

Frequently Asked Questions

What is CVE-2026-80761?
CVE-2026-80761 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-80761?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80761?
CVE-2026-80761 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80761?
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-xhh3-4cvw-88vv",
  "modified" : "2026-09-04T18:31:24Z",
  "published" : "2026-09-04T18:31:24Z",
  "aliases" : [ "CVE-2026-80761" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: zero the sockaddr before returning it in getname\n\niso_sock_getname() fills a struct sockaddr_iso in place and returns its\nsize without clearing it first, so bytes it does not write are copied to\nuser space from the kernel stack. The getsockname(2) and getpeername(2)\npaths both run through do_getsockname(), which hands getname() an\nuninitialized sockaddr_storage on the stack and copies back up to the\nnumber of bytes getname() returns, so the driver has to initialize every\nbyte it accounts for.\n\nTwo ranges are left uninitialized:\n\n  - struct sockaddr_iso is 10 bytes but only 9 are written (family,\n    iso_bdaddr, iso_bdaddr_type), leaking the trailing pad byte on every\n    call.\n\n  - for a broadcast peer (BIS_LINK or PA_LINK) the returned length grows\n    by sizeof(struct sockaddr_iso_bc), but only bc_sid, bc_num_bis and\n    bc_bis are filled; bc_bdaddr and bc_bdaddr_type, the first 7 bytes of\n    that structure, are never written.\n\nAn unprivileged process can open a BTPROTO_ISO socket and reach the pad\nleak with getsockname(); the broadcast leak needs an established BIS/PA\nconnection. l2cap and rfcomm already memset their sockaddr in getname\nfor the same reason; do the same here.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80761"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/190b719b787eb4ca6c25b12fab224806f9108b06"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1f6d1f2611af0eb36b133a41d29ffd2cc2601615"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/884cf2cc957da7ac178a0e6c6c69ddfec0481cc8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9069be87c67f290783b332c4284e09fb89cb9ea7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-04T16:18:01Z"
  }
}