Security readout for executives and security teams
Plain-English summary
A Linux RDMA device-name handling flaw can access memory after it has been freed during device registration or renaming. A local, low-privileged user may be able to trigger the vulnerable path. The supplied CVSS assessment is 7.8, reflecting potentially serious system impact, although the source bundle does not demonstrate real-world exploitation.
Executive priority
Treat this as a high-priority kernel update for RDMA-enabled or multi-user Linux systems. It is less urgent on systems without reachable RDMA functionality or untrusted local access, but those assumptions should be verified. No active exploitation is established by the supplied evidence.
Technical view
CVE-2025-22085 is a CWE-416 use-after-free in Linux RDMA core device naming. Syzbot observed KASAN reading freed name memory through nla_put_string while generating an RDMA netlink notification. The kernel fix retains a device reference during name assignment and waits for its release after renaming, preventing the name from being freed while still in use.
Likely exposure
Exposure is most likely on Linux systems using or permitting RDMA device management, especially where untrusted local users can access the relevant netlink operations. The supplied version data is ambiguous when flattened, so administrators should map their distribution kernel to the cited stable fixes rather than rely solely on version numbers.
Exploitation context
The CVSS vector indicates local access, low attack complexity, low privileges, and no user interaction. Syzbot reproduced the memory-safety failure under KASAN. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or reliable impact beyond the observed use-after-free.
Researcher notes
The report documents a five-byte KASAN read from freed slab memory in nla_put during RDMA device registration. The fix addresses object lifetime around device-name assignment and rename handling. The CVSS claims high confidentiality, integrity, and availability impact, but the bundle does not provide exploitability analysis proving those outcomes.
Mitigation direction
- Install a vendor-supported kernel containing the applicable cited stable fix.
- Prioritize multi-user systems where RDMA functionality is present or available.
- Consult the Linux distribution advisory for backport and package-version mapping.
- If immediate patching is impossible, restrict untrusted local access and review whether RDMA is operationally required.
Validation and detection
- Record the running kernel and distribution package versions.
- Determine whether RDMA drivers, software RDMA, or RDMA netlink management are available.
- Verify the installed package includes the applicable stable fix or vendor backport.
- Confirm systems booted into the updated kernel after maintenance.
- Review vendor security notices because the supplied affected-version representation is ambiguous.
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.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-22085 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/0d6460b9d2a3ee380940bdf47680751ef91cb88eCVE reference, Linux
- https://git.kernel.org/stable/c/56ec8580be5174b2b9774066e60f1aad56d201dbCVE reference, Linux
- https://git.kernel.org/stable/c/edf6b543e81ba68c6dbac2499ab362098a5a9716CVE reference, Linux
- https://git.kernel.org/stable/c/1d6a9e7449e2a0c1e2934eee7880ba8bd1e464cdCVE 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.