Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the Mellanox mlx5 networking driver when connection tracking cleanup runs before traffic-control connection-tracking rules are removed. The result is a kernel warning during cleanup or driver unload paths. The public data does not show remote exploitation, data theft, privilege escalation, or broad internet exposure.
Executive priority
Treat as a targeted operational stability issue, not an emergency internet-facing incident based on current evidence. Patch during the next appropriate kernel maintenance window, faster for network infrastructure relying on mlx5 offload or BlueField devices.
Technical view
The bug is an ordering flaw in mlx5e CT and TC cleanup for uplink representor teardown. CT shared resources can be destroyed before offloaded TC CT tuples are removed, triggering mlx5dr_action_destroy warnings. Kernel stable commits reverse init and cleanup ordering so TC cleanup happens before CT cleanup.
Likely exposure
Exposure appears limited to Linux systems using mlx5/mlx5e hardware and TC connection-tracking offload paths, including environments similar to the BlueField trace. The affected version metadata is incomplete in the bundle, but it names Linux 5.18-era versions and kernel stable fixes.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The described impact is a cleanup-time warning trace, not a demonstrated attacker-controlled exploit path. Operational risk is most relevant where mlx5 offload features are used in production networking.
Researcher notes
Key uncertainty remains impact scope: the source shows a warning trace and cleanup ordering defect, but no CVSS, CWE, exploitability analysis, or distro mapping. Validation should focus on driver, hardware, kernel branch, and offload feature usage rather than generic Linux exposure.
Mitigation direction
Update to a Linux kernel containing the referenced stable mlx5e cleanup-order fixes.
Check your distribution or hardware vendor advisory for the exact fixed kernel build.
Prioritize hosts using Mellanox mlx5, BlueField, TC flower, or connection-tracking offload.
Avoid inventing workarounds; use vendor guidance if patching is delayed.
Validation and detection
Inventory Linux hosts with mlx5_core or mlx5e drivers loaded.
Confirm whether TC connection-tracking offload or uplink representors are in use.
Compare running kernel builds against vendor fixed versions or referenced stable commits.
Review kernel logs for mlx5dr_action_destroy or mlx5_tc_ct_clean warnings during teardown.
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-2022-49338 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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
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.
Feb 26, 2025, 02:10 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.