5.5
MEDIUM CVSS 3.1
CVE-2026-52995
net/rds: zero per-item info buffer before handing it to visitors
Description

In the Linux kernel, the following vulnerability has been resolved: net/rds: zero per-item info buffer before handing it to visitors rds_for_each_conn_info() and rds_walk_conn_path_info() both hand a caller-allocated on-stack u64 buffer to a per-connection visitor and then copy the full item_len bytes back to user space via rds_info_copy() regardless of how much of the buffer the visitor actually wrote. rds_ib_conn_info_visitor() and rds6_ib_conn_info_visitor() only write a subset of their output struct when the underlying rds_connection is not in state RDS_CONN_UP (src/dst addr, tos, sl and the two GIDs via explicit memsets). Several u32 fields (max_send_wr, max_recv_wr, max_send_sge, rdma_mr_max, rdma_mr_size, cache_allocs) and the 2-byte alignment hole between sl and cache_allocs remain as whatever stack contents preceded the visitor call and are then memcpy_to_user()'d out to user space. struct rds_info_rdma_connection and struct rds6_info_rdma_connection are the only rds_info_* structs in include/uapi/linux/rds.h that are not marked __attribute__((packed)), so they have a real alignment hole. The other info visitors (rds_conn_info_visitor, rds6_conn_info_visitor, rds_tcp_tc_info, ...) write all fields of their packed output struct today and are not known to be vulnerable, but a future visitor that adds a conditional write-path would have the same bug. Reproduction on a kernel built without CONFIG_INIT_STACK_ALL_ZERO=y: a local unprivileged user opens AF_RDS, sets SO_RDS_TRANSPORT=IB, binds to a local address on an RDMA-capable netdev (rxe soft-RoCE on any netdev is sufficient), sendto()'s any peer on the same subnet (fails cleanly but installs an rds_connection in the global hash in RDS_CONN_CONNECTING), then calls getsockopt(SOL_RDS, RDS_INFO_IB_CONNECTIONS). The returned 68-byte item contains 26 bytes of stack garbage including kernel text/data pointers: 0..7 0a 63 00 01 0a 63 00 02 src=10.99.0.1 dst=10.99.0.2 8..39 00 ... gids (memset-zeroed) 40..47 e0 92 a3 81 ff ff ff ff kernel pointer (max_send_wr) 48..55 7f 37 b5 81 ff ff ff ff kernel pointer (rdma_mr_max) 56..59 01 00 08 00 rdma_mr_size (garbage) 60..61 00 00 tos, sl 62..63 00 00 alignment padding 64..67 18 00 00 00 cache_allocs (garbage) Fix by zeroing the per-item buffer in both rds_for_each_conn_info() and rds_walk_conn_path_info() before invoking the visitor. This covers the IPv4/IPv6 IB visitors and hardens all current and future visitors against the same class of bug. No functional change for visitors that fully populate their output. Changes in v2: - retarget at the net tree (subject prefix "[PATCH net v2]", net/rds: prefix in the title) - pick up Reviewed-by tags from Sharath Srinivasan and Allison Henderson

INFO

Published Date :

June 24, 2026, 5:17 p.m.

Last Modified :

July 15, 2026, 1:06 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-52995 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Zero per-item buffer before visitor to prevent stack garbage disclosure.
  • Zero per-item buffer before visitor call.
  • Apply the provided patch to the Linux kernel.
  • Ensure stack is zeroed if CONFIG_INIT_STACK_ALL_ZERO is not enabled.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-52995 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-52995 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-52995 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-52995 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Jul. 15, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE NVD-CWE-noinfo
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.141 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.91 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.175 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.209 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.30 up to (excluding) 5.10.258
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/0797b2e6901827694aa9c34c4c72118c8c97fba1 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/5e67cc262afb384e835c3327e9d954eeaedc6a87 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/81651e9d7dea1c048d2952f57632a042931d7b43 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/912ba2e5704fdb8bc5decda96dfc1a57838f0099 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/91ce1bb6e4194dc2321748f68145359dcf86e350 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/b6ba93a7b71ed443c9843eb12d27ed86f1e52694 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/c7cb9eed8215a790f052f49cdccf577720d2bb62 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/c88eb7e8d8397a8c1db59c425332c5a30b2a1682 Types: Patch
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jun. 24, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': '81651e9d7dea1c048d2952f57632a042931d7b43', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': '0797b2e6901827694aa9c34c4c72118c8c97fba1', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': '5e67cc262afb384e835c3327e9d954eeaedc6a87', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': 'b6ba93a7b71ed443c9843eb12d27ed86f1e52694', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': 'c7cb9eed8215a790f052f49cdccf577720d2bb62', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': '91ce1bb6e4194dc2321748f68145359dcf86e350', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': '912ba2e5704fdb8bc5decda96dfc1a57838f0099', 'versionType': 'git'}, {'status': 'affected', 'version': 'ec16227e14141e4fd7ae76354c09dadfe2449d9e', 'lessThan': 'c88eb7e8d8397a8c1db59c425332c5a30b2a1682', 'versionType': 'git'}], 'programFiles': ['net/rds/connection.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2.6.30'}, {'status': 'unaffected', 'version': '0', 'lessThan': '2.6.30', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.258', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.209', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.175', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.141', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.91', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.33', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.10', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/rds/connection.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: net/rds: zero per-item info buffer before handing it to visitors rds_for_each_conn_info() and rds_walk_conn_path_info() both hand a caller-allocated on-stack u64 buffer to a per-connection visitor and then copy the full item_len bytes back to user space via rds_info_copy() regardless of how much of the buffer the visitor actually wrote. rds_ib_conn_info_visitor() and rds6_ib_conn_info_visitor() only write a subset of their output struct when the underlying rds_connection is not in state RDS_CONN_UP (src/dst addr, tos, sl and the two GIDs via explicit memsets). Several u32 fields (max_send_wr, max_recv_wr, max_send_sge, rdma_mr_max, rdma_mr_size, cache_allocs) and the 2-byte alignment hole between sl and cache_allocs remain as whatever stack contents preceded the visitor call and are then memcpy_to_user()'d out to user space. struct rds_info_rdma_connection and struct rds6_info_rdma_connection are the only rds_info_* structs in include/uapi/linux/rds.h that are not marked __attribute__((packed)), so they have a real alignment hole. The other info visitors (rds_conn_info_visitor, rds6_conn_info_visitor, rds_tcp_tc_info, ...) write all fields of their packed output struct today and are not known to be vulnerable, but a future visitor that adds a conditional write-path would have the same bug. Reproduction on a kernel built without CONFIG_INIT_STACK_ALL_ZERO=y: a local unprivileged user opens AF_RDS, sets SO_RDS_TRANSPORT=IB, binds to a local address on an RDMA-capable netdev (rxe soft-RoCE on any netdev is sufficient), sendto()'s any peer on the same subnet (fails cleanly but installs an rds_connection in the global hash in RDS_CONN_CONNECTING), then calls getsockopt(SOL_RDS, RDS_INFO_IB_CONNECTIONS). The returned 68-byte item contains 26 bytes of stack garbage including kernel text/data pointers: 0..7 0a 63 00 01 0a 63 00 02 src=10.99.0.1 dst=10.99.0.2 8..39 00 ... gids (memset-zeroed) 40..47 e0 92 a3 81 ff ff ff ff kernel pointer (max_send_wr) 48..55 7f 37 b5 81 ff ff ff ff kernel pointer (rdma_mr_max) 56..59 01 00 08 00 rdma_mr_size (garbage) 60..61 00 00 tos, sl 62..63 00 00 alignment padding 64..67 18 00 00 00 cache_allocs (garbage) Fix by zeroing the per-item buffer in both rds_for_each_conn_info() and rds_walk_conn_path_info() before invoking the visitor. This covers the IPv4/IPv6 IB visitors and hardens all current and future visitors against the same class of bug. No functional change for visitors that fully populate their output. Changes in v2: - retarget at the net tree (subject prefix "[PATCH net v2]", net/rds: prefix in the title) - pick up Reviewed-by tags from Sharath Srinivasan and Allison Henderson
    Added Reference https://git.kernel.org/stable/c/0797b2e6901827694aa9c34c4c72118c8c97fba1
    Added Reference https://git.kernel.org/stable/c/5e67cc262afb384e835c3327e9d954eeaedc6a87
    Added Reference https://git.kernel.org/stable/c/81651e9d7dea1c048d2952f57632a042931d7b43
    Added Reference https://git.kernel.org/stable/c/912ba2e5704fdb8bc5decda96dfc1a57838f0099
    Added Reference https://git.kernel.org/stable/c/91ce1bb6e4194dc2321748f68145359dcf86e350
    Added Reference https://git.kernel.org/stable/c/b6ba93a7b71ed443c9843eb12d27ed86f1e52694
    Added Reference https://git.kernel.org/stable/c/c7cb9eed8215a790f052f49cdccf577720d2bb62
    Added Reference https://git.kernel.org/stable/c/c88eb7e8d8397a8c1db59c425332c5a30b2a1682
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.