CVE-2026-97476: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-976h-hf4r-h525
Published
Advisory Summary

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

CVE Identifier CVE-2026-97476
GHSA Identifier GHSA-976h-hf4r-h525
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-97476

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-97476, 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: rds: filter RDS_INFO_* getsockopt by caller's netns The RDS_INFO_* family of getsockopt(2) options reads several file-scope global lists that are not per-netns: rds_sock_info / rds6_sock_info, rds_sock_inc_info / rds6_sock_inc_info -> rds_sock_list rds_tcp_tc_info / rds6_tcp_tc_info -> rds_tcp_tc_list rds_conn_info / rds6_conn_info, rds_conn_message_info_cmn (for the *_SEND_MESSAGES and *_RETRANS_MESSAGES variants), rds_for_each_conn_info (for RDS_INFO_IB_CONNECTIONS) -> rds_conn_hash[] The handlers do not filter by the caller's network namespace. rds_info_getsockopt() has no netns or capable() check, and rds_create() has no capable() check, so AF_RDS is reachable from an unprivileged user namespace. As a result, an unprivileged caller in a fresh user_ns plus netns can read the bound address and sock inode of every RDS socket on the host, the peer address of incoming messages on every RDS socket on the host, the peer address and TCP sequence numbers of every rds-tcp connection on the host, and the peer address and RDS sequence numbers of every RDS connection on the host. The rds-tcp transport is reachable from a non-initial netns (see rds_set_transport()), so a one-shot init_net gate at rds_info_getsockopt() would deny legitimate per-netns visibility to rds-tcp callers. Instead, filter at each handler by comparing the netns of the caller's socket to the netns of the list entry, or to rds_conn_net(conn) for connection paths. Only copy entries whose netns matches the caller. Counters (RDS_INFO_COUNTERS) are aggregate statistics and remain global. Reproducer (KASAN VM, rds and rds_tcp loaded): an AF_RDS socket binds 127.0.0.1:4242 in init_net as root. A child process enters a fresh user_ns plus netns and opens AF_RDS there, then calls getsockopt(SOL_RDS, RDS_INFO_SOCKETS). Before this change, the child sees the init_net socket. After this change, the child sees zero entries. Drop the rds_sock_count, rds_tcp_tc_count, and rds6_tcp_tc_count globals. v2 used them for the size precheck and lens->nr; v3 replaced the precheck with a per-ns count from a first pass over the list, so the globals have no remaining readers. The matching increments and decrements in rds_create()/rds_destroy_sock() and rds_tcp_set_callbacks()/rds_tcp_restore_callbacks() go away with them. Reported by the kernel test robot under clang W=1.

References

Frequently Asked Questions

What is CVE-2026-97476?
CVE-2026-97476 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-97476?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97476?
CVE-2026-97476 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97476?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-976h-hf4r-h525",
  "modified" : "2026-10-03T12:31:13Z",
  "published" : "2026-09-24T18:31:34Z",
  "aliases" : [ "CVE-2026-97476" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nrds: filter RDS_INFO_* getsockopt by caller's netns\n\nThe RDS_INFO_* family of getsockopt(2) options reads several\nfile-scope global lists that are not per-netns:\n\n  rds_sock_info / rds6_sock_info,\n  rds_sock_inc_info / rds6_sock_inc_info        -> rds_sock_list\n  rds_tcp_tc_info / rds6_tcp_tc_info            -> rds_tcp_tc_list\n  rds_conn_info / rds6_conn_info,\n  rds_conn_message_info_cmn (for the *_SEND_MESSAGES and\n  *_RETRANS_MESSAGES variants),\n  rds_for_each_conn_info (for RDS_INFO_IB_CONNECTIONS)\n                                                -> rds_conn_hash[]\n\nThe handlers do not filter by the caller's network namespace.\nrds_info_getsockopt() has no netns or capable() check, and\nrds_create() has no capable() check, so AF_RDS is reachable from\nan unprivileged user namespace. As a result, an unprivileged\ncaller in a fresh user_ns plus netns can read the bound address\nand sock inode of every RDS socket on the host, the peer address\nof incoming messages on every RDS socket on the host, the peer\naddress and TCP sequence numbers of every rds-tcp connection on\nthe host, and the peer address and RDS sequence numbers of every\nRDS connection on the host.\n\nThe rds-tcp transport is reachable from a non-initial netns (see\nrds_set_transport()), so a one-shot init_net gate at\nrds_info_getsockopt() would deny legitimate per-netns visibility\nto rds-tcp callers. Instead, filter at each handler by comparing\nthe netns of the caller's socket to the netns of the list entry,\nor to rds_conn_net(conn) for connection paths. Only copy entries\nwhose netns matches the caller. Counters (RDS_INFO_COUNTERS) are\naggregate statistics and remain global.\n\nReproducer (KASAN VM, rds and rds_tcp loaded): an AF_RDS socket\nbinds 127.0.0.1:4242 in init_net as root. A child process enters\na fresh user_ns plus netns and opens AF_RDS there, then calls\ngetsockopt(SOL_RDS, RDS_INFO_SOCKETS). Before this change, the\nchild sees the init_net socket. After this change, the child\nsees zero entries.\n\nDrop the rds_sock_count, rds_tcp_tc_count, and rds6_tcp_tc_count\nglobals. v2 used them for the size precheck and lens->nr; v3\nreplaced the precheck with a per-ns count from a first pass over\nthe list, so the globals have no remaining readers. The matching\nincrements and decrements in rds_create()/rds_destroy_sock() and\nrds_tcp_set_callbacks()/rds_tcp_restore_callbacks() go away with\nthem. Reported by the kernel test robot under clang W=1.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97476"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/093f172296d32499ffac7809629b206178776eb6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/64ca5839916176c3451f61a2c7178033423c67d7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/65fae4b42269dbea7e3842ae4dd0786162c6248e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8b04dda272c30d46834bb03dd2895b08c090483b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c4081e49ebe0e3160c4b70ec7639494792dee206"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c96a5209dda666004b8ee1ed7f0d493d09a4f200"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f05142d0eeaa6e8227511c88e10a2b8fe7a78fc4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T17:17:24Z"
  }
}