Security readout for executives and security teams
Plain-English summary
A race in the Linux InfiniBand connection manager can trigger an incorrect kernel warning while an older message is being released. The supplied CVSS assessment identifies availability, rather than confidentiality or integrity, as the impact. Systems using affected Linux kernels and InfiniBand/RDMA functionality deserve priority review, although the bundle does not establish real-world exploitation.
Executive priority
Treat this as a high-priority availability issue for organizations operating InfiniBand or RDMA on affected kernels, especially critical compute, storage, or clustered environments. Prioritize inventory and supported kernel updates. Lower the urgency for systems demonstrably outside the affected versions or without the relevant functionality, while documenting that conclusion.
Technical view
An IB/cm send-completion handler may execute after its cm_id has advanced to another message. The reused cm_free_priv_msg() helper expects the cm_id lock and current outstanding message to match, causing an assertion or WARN when freeing the older message. The referenced kernel commits remove that inappropriate check and warning. The bundle scores this CVSS 3.1 7.5 with network reachability and high availability impact.
Likely exposure
The bundle marks Linux kernel versions spanning 6.13 through entries including 6.15.3 and 6.16 as affected, but its version-range encoding is ambiguous. Practical exposure is most likely where an affected kernel's InfiniBand connection-manager functionality is present and used. Distribution backports may alter exposure, so package versions alone may not be conclusive.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. The CVSS vector describes unauthenticated, low-complexity network attack potential, but the bundle does not explain required InfiniBand/RDMA access, reliable triggering conditions, or observed operational incidents.
Researcher notes
The source bundle provides no CWE, proof of exploitation, trigger details, or precise distribution-package mapping. Its affected-version data is internally difficult to interpret, including duplicated commit identifiers and several bare version values. Validate ancestry and backports against the two upstream stable commits. Avoid inferring memory corruption or remote code execution; only availability impact is represented by the supplied CVSS vector.
Mitigation direction
- Inventory Linux kernel versions on systems using InfiniBand or RDMA connection management.
- Apply a vendor-supported kernel containing the referenced IB/cm correction.
- Check distribution advisories for backported fixes before relying on upstream version numbers.
- Prioritize externally or broadly reachable RDMA fabrics and availability-sensitive systems.
- Use vendor guidance if an immediate supported kernel update is unavailable.
Validation and detection
- Confirm each system's running kernel and distribution package build.
- Determine whether InfiniBand/RDMA connection-manager functionality is installed, enabled, and used.
- Verify vendor changelogs or source history include either referenced correction.
- Review kernel logs for related IB/cm warnings without treating their absence as proof of safety.
- Retest affected RDMA workloads after updating and confirm the warning no longer appears.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2025-38287 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6LinuxVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/fc096a0cd2017cb0aa1e7fb83131410af9283910CVE reference, Linux
- https://git.kernel.org/stable/c/7590649ee7af381a9d1153143026dec124c5798eCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.