LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53371: net/mlx5e: fix memory leak in mlx5e_fs_tt_redirect_any_create

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: fix memory leak in mlx5e_fs_tt_redirect_any_create The memory pointed to by the fs->any pointer is not freed in the error path of mlx5e_fs_tt_redirect_any_create, which can lead to a memory leak. Fix by freeing the memory in the error path, thereby making the error path identical to mlx5e_fs_tt_redirect_any_destroy().

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in a network driver error path. A local low-privileged user could potentially cause availability impact if the affected path is reached repeatedly. The sources show a kernel fix, not evidence of public exploitation.

Executive priority

Treat this as a moderate availability risk. It is worth patching through normal kernel maintenance, with higher urgency for shared Linux systems or infrastructure using mlx5e networking. There is no source-backed evidence of active exploitation.

Technical view

CVE-2023-53371 is CWE-401 in net/mlx5e. mlx5e_fs_tt_redirect_any_create fails to free fs->any on an error path, causing a memory leak. CVSS 3.1 is 5.5: local access, low complexity, low privileges, no user interaction, availability impact only.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions and the mlx5e network driver code path. The record lists Linux kernel versions including 5.13, 6.1.40, 6.4.5, and 6.5. Distribution backports may change real exposure.

Exploitation context

The source bundle does not show KEV listing, active exploitation, public exploit availability, or remote attack capability. The CVSS vector requires local low-privileged access and indicates availability impact, not confidentiality or integrity compromise.

Researcher notes

The record describes a resolved Linux kernel memory leak where the create error path did not match the destroy path. Analysis should focus on affected kernel lineage, driver reachability, and whether distro kernels incorporated the three stable commits.

Mitigation direction

  • Update to a kernel or distro package containing the referenced stable fixes.
  • Confirm vendor or distribution advisories for backported kernel fixes.
  • Prioritize systems using mlx5e networking or affected kernel branches.
  • Apply normal local-access hardening for shared or multi-user Linux hosts.

Validation and detection

  • Inventory Linux kernel versions on systems using mlx5e networking.
  • Check whether installed kernel packages include the referenced stable commits.
  • Review vendor kernel changelogs for CVE-2023-53371 or the mlx5e fix.
  • Monitor affected systems for unusual kernel memory growth until patched.
Prepared
Confidence
high
Sources
5

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.

cwe · low confidence lookup

CWE-401: 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 lookup
cve · low confidence lookup

CVE-2023-53371 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53371Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0f575c20bf0686caf3d82d6c626c2e1e4a4c36e6, 0f575c20bf0686caf3d82d6c626c2e1e4a4c36e6, 0f575c20bf0686caf3d82d6c626c2e1e4a4c36e6unaffected
LinuxLinux5.13, 0, 6.1.40, 6.4.5, 6.5affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.