Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a cleanup bug in the mlx5 network driver. If enabling vport QoS fails, a scheduling node is not freed, creating a resource leak. Sources do not provide CVSS, CWE, attack requirements, or exploitation evidence.
Executive priority
Handle through normal kernel maintenance unless vendor guidance raises impact. There is no sourced evidence of exploitation or high business urgency, but exposed infrastructure hosts should still receive routine kernel updates.
Technical view
The flaw is in net/mlx5 vport QoS error handling. On enable failure, the driver omitted freeing a scheduling node and resetting its pointer to NULL. The source bundle lists Linux as affected, including version data around 6.13, 6.13.6, and 6.14.
Likely exposure
Exposure is likely limited to Linux systems using mlx5 networking functionality where vport QoS operations can be reached. The sources do not define remote reachability, privilege requirements, or tenant impact.
Exploitation context
No active exploitation is indicated. The CVE is not marked KEV, and the provided sources do not describe public exploitation, exploitability conditions, or practical abuse paths.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or attack preconditions are provided. Analysis should focus on confirming affected kernel branches, mlx5 deployment, and whether the cleanup leak can cause meaningful availability impact.
Mitigation direction
- Check kernel vendor advisories for affected package versions and backports.
- Prioritize updates on hosts using Mellanox/NVIDIA mlx5 networking features.
- Apply kernel updates containing the referenced stable fixes when available.
- Track distribution-specific CVE status before scheduling production reboots.
Validation and detection
- Inventory Linux kernel versions on systems with mlx5 hardware or drivers.
- Confirm whether vport QoS features are enabled or operationally relevant.
- Compare installed kernel packages against distribution CVE advisories.
- Verify updated kernels include the referenced stable commits or vendor backports.
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-21882 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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/fead368502bce0e10bea7c0d2895b2fa0c6c10aaCVE reference, Linux
- https://git.kernel.org/stable/c/7f3528f7d2f98b70e19a6bb7b130fc82c079ac54CVE 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.