Security readout for executives and security teams
Plain-English summary
This is a Linux kernel mlx5 networking driver bug. During E-Switch offload pairing, the driver could consider devices that were not LAG-capable and call a device lookup path without the required lock. The public record shows a kernel warning during devlink E-Switch configuration, not proven data compromise or active exploitation.
Executive priority
Treat as a targeted infrastructure maintenance item, not an emergency based on current evidence. Patch during the next kernel maintenance window for hosts using mlx5 networking offloads, and escalate if vendor advisories assign higher severity for your distribution.
Technical view
The fix filters devcom OFFLOADS pairing to devices supporting LAG. The issue was exposed after a related commit added an assertion that mlx5_get_next_phys_dev() must hold the interface lock. The trace involves mlx5_esw_offloads_devcom_event(), esw_offloads_enable(), and devlink E-Switch mode setting in mlx5_core.
Likely exposure
Exposure appears limited to Linux systems using mlx5_core with Mellanox/NVIDIA mlx5 networking, especially E-Switch offloads, devlink configuration, and LAG-capable hardware paths. The source bundle does not provide CPEs or complete distribution package mapping.
Exploitation context
No KEV listing, exploit status, or weaponized public exploit is cited in the bundle. The evidence describes a kernel warning triggered during device configuration, so exploitation impact and attacker prerequisites are not established from these sources.
Researcher notes
The record lacks CVSS, CWE, CPEs, exploit evidence, and detailed impact beyond the warning trace. Version data is partially structured and should be validated against upstream stable commits and downstream distro backports before marking assets vulnerable.
Mitigation direction
Apply Linux kernel or distribution updates containing the referenced stable fixes.
Prioritize systems using mlx5_core, E-Switch offloads, devlink, or LAG configurations.
Check vendor or distribution advisories for exact fixed package versions.
Avoid ad hoc driver changes unless supported by vendor guidance.
Validation and detection
Inventory Linux hosts with mlx5_core loaded or Mellanox/NVIDIA mlx5 adapters installed.
Check kernel versions and vendor changelogs for the referenced stable commits.
Review logs for mlx5_get_next_phys_dev or mlx5_esw_offloads warnings.
Confirm devlink E-Switch and LAG usage on affected hosts.
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-49333 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
4Source 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.