CVE-2024-26872: RDMA/srpt: Do not register event handler until srpt device is fully setup
In the Linux kernel, the following vulnerability has been resolved:
RDMA/srpt: Do not register event handler until srpt device is fully setup
Upon rare occasions, KASAN reports a use-after-free Write
in srpt_refresh_port().
This seems to be because an event handler is registered before the
srpt device is fully setup and a race condition upon error may leave a
partially setup event handler in place.
Instead, only register the event handler after srpt device initialization
is complete.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux RDMA SCSI target component can cause kernel memory to be used after it is freed. A locally authenticated, low-privileged user may be able to trigger serious system compromise or disruption. Exposure is concentrated on systems using the SRP target functionality, not every Linux host.
Executive priority
Treat as high priority for systems actively using SRP target services, especially shared or locally accessible infrastructure. For hosts without this functionality, verify non-exposure and handle through normal kernel patching. No supplied evidence supports an emergency response for active exploitation.
Technical view
The srpt event handler could be registered before device initialization completed. If initialization then failed, the partially configured handler could remain and race with cleanup, producing a use-after-free write in srpt_refresh_port(). The stable fix delays handler registration until initialization completes.
Likely exposure
Prioritize Linux storage, virtualization, or appliance systems where RDMA/SRP target functionality is enabled or loaded. The supplied version data identifies affected Linux releases but is ambiguous enough that exact package exposure should be confirmed through distribution or appliance-vendor advisories.
Exploitation context
The CVSS vector describes local access with low privileges, no user interaction, and potentially complete confidentiality, integrity, and availability impact. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The vulnerability is a rare initialization and cleanup race involving event-handler lifetime. KASAN observed a use-after-free write in srpt_refresh_port(). The source bundle does not identify a CWE, reliable trigger conditions, or exploitation in the wild. Its affected-version presentation should not be used alone for package-level conclusions.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix.
Check distribution and appliance advisories for exact fixed package versions.
Restrict local access on exposed systems until updates are applied.
Disable unused RDMA/SRP target functionality according to vendor guidance.
Validation and detection
Inventory kernel versions on systems providing RDMA-backed storage services.
Confirm whether the srpt component is enabled, loaded, or required.
Map installed packages to vendor-fixed releases or referenced stable commits.
Review kernel and KASAN logs for srpt initialization errors or use-after-free reports.
Retest required RDMA storage operations after updating or disabling functionality.
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-26872 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.