In the Linux kernel, the following vulnerability has been resolved:
net: mctp: Set SOCK_RCU_FREE
Bind lookup runs under RCU, so ensure that a socket doesn't go away in
the middle of a lookup.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can allow an MCTP socket to disappear while the kernel is still looking it up, creating unsafe memory handling. The supplied CVSS score is 8.8, indicating potentially serious confidentiality, integrity, and availability impact. Practical exposure depends on whether an affected kernel and MCTP networking are present.
Executive priority
Treat this as a high-priority kernel update for infrastructure using MCTP, especially where adjacent components are not fully trusted. Patch through normal emergency maintenance based on exposure. Systems without MCTP use appear less likely to be practically exposed, but that conclusion should be verified rather than assumed.
Technical view
MCTP bind lookup executes under read-copy-update protection, but affected sockets were not marked for RCU-deferred freeing. Concurrent socket teardown could therefore race with lookup and leave the lookup operating on freed memory. Linux stable fixes set SOCK_RCU_FREE so socket reclamation waits for applicable RCU readers.
Likely exposure
Potentially exposed systems run an affected Linux kernel and enable or use the kernel's MCTP subsystem. The CVSS vector requires adjacent-network access, not ordinary internet reachability. The supplied version data names affected release points but does not clearly define every distribution-specific range, so confirm exposure through vendor advisories and backport records.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public exploit. Exploitation would require reaching an applicable adjacent MCTP context and triggering a socket-lifetime race. Reliability, prerequisites, and demonstrated real-world impact are not established by the supplied sources.
Researcher notes
The core issue is an RCU socket-lifetime race in MCTP bind lookup. The source bundle provides multiple Linux stable commits, suggesting fixes across supported branches. It does not provide a reproducer, affected configuration details, exploitation telemetry, or authoritative distribution-by-distribution version ranges. Avoid interpreting the listed release points as complete package boundaries.
Mitigation direction
Install a vendor-supported kernel containing the upstream fix or an equivalent backport.
Reboot into the corrected kernel after installation; merely installing a package may leave the vulnerable kernel running.
Prioritize systems where MCTP is enabled, actively used, or reachable from less-trusted adjacent components.
If patching is delayed, consult vendor guidance before disabling or restricting MCTP functionality.
Validation and detection
Inventory running kernel versions and identify systems with MCTP support enabled or in use.
Compare each distribution kernel against its vendor advisory and backport changelog.
Verify the running kernel includes the applicable stable fix or equivalent SOCK_RCU_FREE change.
Confirm patched systems restarted successfully and are running the intended corrected kernel.
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-2025-37790 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.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
CVSS vector scores
1 official score
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.