Out-of-bounds kernel access during connection cleanup
Published Oct 21, 2024 · Updated Aug 5, 2026
Out-of-bounds access in the Linux kernel allows local users to access kernel memory during failed RTRS client connection setup. The init_conns() error path leaves cid equal to con_num after create_con() or create_cm() fails, so its cleanup loop indexes one connection beyond the allocated array. Reachability requires the RTRS client path and a connection-creation failure; the public record does not specify whether the access reads or writes memory or report a concrete outcome.
Summary
What happened
Out-of-bounds access in the Linux kernel allows local users to access kernel memory during failed RTRS client connection setup. The init_conns() error path leaves cid equal to con_num after create_con() or create_cm() fails, so its cleanup loop indexes one connection beyond the allocated array. Reachability requires the RTRS client path and a connection-creation failure; the public record does not specify whether the access reads or writes memory or report a concrete outcome.
The record
- CVE
- CVE-2024-47695
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8
- Affected versionversion=6a98d71daea186247005099758af549e6afdd244 <01b9be936ee8839ab9f83a7e84ee02ac6c8303c4
- Affected versionversion=6a98d71daea186247005099758af549e6afdd244 <0429a4e972082e3a2351da414b1c017daaf8aed2
- Affected versionversion=6a98d71daea186247005099758af549e6afdd244 <1c50e0265fa332c94a4a182e4efa0fc70d8fad94
- Affected versionversion=6a98d71daea186247005099758af549e6afdd244 <3e4289b29e216a55d08a89e126bc0b37cbad9f38
- Affected versionversion=6a98d71daea186247005099758af549e6afdd244 <5ac73f8191f3de41fef4f934d84d97f3aadb301f
- Affected versionversion=6a98d71daea186247005099758af549e6afdd244 <c8b7f3d9fada0d4b4b7db86bf7345cd61f1d972e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
No sourced classifications are available.
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