Local system crash via RDS trace index
Published Jan 23, 2024 · Updated Nov 4, 2025
An out-of-bounds read in the Linux kernel RDS implementation through 6.7.1 allows local users to crash the system via a socket option. rds_recv_track_latency accepts a receive-trace position equal to RDS_MSG_RX_DGRAM_TRACE_MAX, and rds_cmsg_recv adds one before indexing a four-element latency array. Low-privileged local access and the RDS protocol are required; the demonstrated consequence is an availability-only kernel crash.
Summary
What happened
An out-of-bounds read in the Linux kernel RDS implementation through 6.7.1 allows local users to crash the system via a socket option. rds_recv_track_latency accepts a receive-trace position equal to RDS_MSG_RX_DGRAM_TRACE_MAX, and rds_cmsg_recv adds one before indexing a four-element latency array. Low-privileged local access and the RDS protocol are required; the demonstrated consequence is an availability-only kernel crash.
The record
- CVE
- CVE-2024-23849
- Published
- Jan 23, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-193, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo