Kernel crash via RXE response use-after-free
Published Jun 19, 2024 · Updated Aug 5, 2026
Use-after-free in Linux 4.12 and later allows attackers to crash the kernel during RDMA RXE response packet processing. The rxe_comp_queue_pkt function enqueues an incoming response skb before incrementing its hardware counter, allowing a concurrent completer thread to free the skb before that dereference. The race requires RXE traffic and concurrent completer execution and was observed only infrequently during high-scale testing; success causes a kernel segmentation fault.
Summary
What happened
Use-after-free in Linux 4.12 and later allows attackers to crash the kernel during RDMA RXE response packet processing. The rxe_comp_queue_pkt function enqueues an incoming response skb before incrementing its hardware counter, allowing a concurrent completer thread to free the skb before that dereference. The race requires RXE traffic and concurrent completer execution and was observed only infrequently during high-scale testing; success causes a kernel segmentation fault.
The record
- CVE
- CVE-2024-38544
- Published
- Jun 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 19, 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=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <21b4c6d4d89030fd4657a8e7c8110fd941049794
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <2b23b6097303ed0ba5f4bc036a1c07b6027af5c6
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <30df4bef8b8e183333e9b6e9d4509d552c7da6eb
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <bbad88f111a1829f366c189aa48e7e58e57553fc
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <c91fb72a2ca6480d8d77262eef52dc5b178463a3
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <de5a059e36657442b5637cc16df5163e435b9cb4
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <e0e14dd35d4242340c7346aac60c7ff8fbf87ffc
- Affected versionversion=0b1e5b99a48b5b810e3e38f1d6e0d39306b99ec0 <faa8d0ecf6c9c7c2ace3ca3e552180ada6f75e19
- Affected versionversion=4.12
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