CVE-2022-49025: net/mlx5e: Fix use-after-free when reverting termination table
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Fix use-after-free when reverting termination table
When having multiple dests with termination tables and second one
or afterwards fails the driver reverts usage of term tables but
doesn't reset the assignment in attr->dests[num_vport_dests].termtbl
which case a use-after-free when releasing the rule.
Fix by resetting the assignment of termtbl to null.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49025 is a Linux kernel flaw in the mlx5e network driver. Under a specific error path, the driver can keep a pointer to freed memory, creating a use-after-free condition when a rule is later released. Public sources do not provide CVSS, impact detail, or evidence of exploitation.
Executive priority
Medium operational priority, with urgency driven by whether critical systems use mlx5e networking. Patch through normal kernel maintenance unless vendor advisories or local exposure analysis raise severity.
Technical view
The bug is in net/mlx5e termination table rollback. If multiple destinations use termination tables and a later destination fails, rollback frees the termination table but leaves attr->dests[num_vport_dests].termtbl assigned. Releasing the rule can then dereference freed memory. The fix resets that termtbl assignment to null.
Likely exposure
Exposure appears limited to Linux kernels containing the affected mlx5e driver code path, especially systems using Mellanox mlx5 networking features. The source bundle lists Linux as affected and provides stable kernel fix commits, but it does not map exposure to distributions, packages, or configurations.
Exploitation context
The CVE is not listed as KEV in the provided bundle. No cited source states active exploitation, public exploit availability, or remote exploitability. Treat this as a kernel memory-safety issue requiring patch tracking, not as confirmed exploited activity.
Researcher notes
Evidence is sparse: no CVSS, CWE, distro matrix, exploit status, or detailed impact is provided. Analysis should stay tied to the Linux mlx5e rollback use-after-free and the stable commits until vendor advisories add package-level details.
Mitigation direction
Apply a vendor-supported Linux kernel update that includes the referenced stable fixes.
Prioritize systems using mlx5e or Mellanox mlx5 networking hardware and features.
Check Linux distribution advisories for package-specific fixed versions.
Avoid relying on unsupported kernel branches for security-sensitive network hosts.
Track vendor guidance if immediate patching is not operationally possible.
Validation and detection
Inventory Linux hosts for mlx5e driver usage and kernel versions.
Compare installed kernel builds with distribution advisories and stable fix commits.
Confirm patched hosts run an updated kernel after reboot.
Review network/security appliances separately if they embed Linux kernels.
Document any unpatched exposed systems and compensating operational constraints.
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-49025 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.