Kernel memory corruption via premature CM ID teardown
Published Aug 17, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux RDMA/iWARP connection manager allows remote attackers to corrupt kernel memory during CM ID teardown. rdma_destroy_id() frees the CM ID and its rdma_id_private while cm_work_handler() can still process queued work through the freed private structure. Reachability requires the iWARP RDMA connection-management path; the published record does not distinguish code execution from a host crash.
Summary
What happened
Use-after-free in the Linux RDMA/iWARP connection manager allows remote attackers to corrupt kernel memory during CM ID teardown. rdma_destroy_id() frees the CM ID and its rdma_id_private while cm_work_handler() can still process queued work through the freed private structure. Reachability requires the iWARP RDMA connection-management path; the published record does not distinguish code execution from a host crash.
The record
- CVE
- CVE-2024-42285
- Published
- Aug 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 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=4.8
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <557d035fe88d78dd51664f4dc0e1896c04c97cf6
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <7f25f296fc9bd0435be14e89bf657cd615a23574
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <94ee7ff99b87435ec63211f632918dc7f44dac79
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <aee2424246f9f1dadc33faa78990c1e2eb7826e4
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <d91d253c87fd1efece521ff2612078a35af673c6
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <dc8074b8901caabb97c2d353abd6b4e7fa5a59a5
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <ee39384ee787e86e9db4efb843818ef0ea9cb8ae
- Affected versionversion=59c68ac31e15ad09d2cb04734e3c8c544a95f8d4 <ff5bbbdee08287d75d72e65b72a2b76d9637892a
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
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