CVE-2024-38545: RDMA/hns: Fix UAF for cq async event
In the Linux kernel, the following vulnerability has been resolved:
RDMA/hns: Fix UAF for cq async event
The refcount of CQ is not protected by locks. When CQ asynchronous
events and CQ destruction are concurrent, CQ may have been released,
which will cause UAF.
Use the xa_lock() to protect the CQ refcount.
Security readout for executives and security teams
Plain-English summary
CVE-2024-38545 is a Linux kernel use-after-free issue in the HNS RDMA driver. A timing race between an asynchronous completion queue event and queue destruction can cause the kernel to use memory after it was released. The sources do not provide CVSS, impact, or attacker-prerequisite details.
Executive priority
Medium operational priority where HNS RDMA is present; lower priority for fleets without that driver path. Because severity and exploitation details are missing, handle through kernel patch governance rather than emergency response unless vendor guidance elevates urgency.
Technical view
The bug is in RDMA/hns completion queue handling. The CQ refcount was not lock-protected; concurrent CQ asynchronous events and CQ teardown could release the CQ before event handling finished, causing UAF. The kernel fix protects the CQ refcount with xa_lock().
Likely exposure
Exposure appears limited to Linux systems using the HNS RDMA driver path, commonly tied to HiSilicon RDMA-capable environments. General Linux systems without that driver or hardware path are less likely to be exposed. Version data in the bundle identifies Linux kernel branches and stable commits but not distro package mappings.
Exploitation context
The bundle states KEV is false and provides no evidence of active exploitation. It also does not describe a public exploit, remote reachability, privileges required, or reliable impact. Treat exploitation assumptions as unknown until vendor or distro advisories add detail.
Researcher notes
The public record is sparse: no CVSS, CWE, impact statement, or attacker model is provided. The key evidence is the kernel commit rationale: a race on CQ refcount during async event handling and destruction, fixed by locking. Avoid assuming exploitability beyond the documented UAF condition.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Prioritize Linux hosts using HNS RDMA hardware or the RDMA/hns driver.
Map running distro kernels to vendor advisories for CVE-2024-38545.
If updates are unavailable, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory hosts with RDMA support and HNS driver usage.
Check running kernel versions against distro CVE-2024-38545 advisories.
Confirm the kernel includes the RDMA/hns CQ refcount locking fix.
Review change records to ensure patched kernels are deployed and booted.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-38545 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.