LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54169: net/mlx5e: fix memory leak in mlx5e_ptp_open

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: fix memory leak in mlx5e_ptp_open When kvzalloc_node or kvzalloc failed in mlx5e_ptp_open, the memory pointed by "c" or "cparams" is not freed, which can lead to a memory leak. Fix by freeing the array in the error path.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in the mlx5e network driver error path. If certain memory allocations fail while opening PTP support, previously allocated memory is not released. The supplied sources do not show active exploitation, CVSS scoring, or a clear remote attack path.

Executive priority

Treat as routine kernel maintenance unless affected mlx5e systems show memory pressure or availability concerns. There is no supplied evidence of active exploitation or severe impact, but kernel fixes should still be included in normal patch cycles.

Technical view

CVE-2023-54169 affects Linux kernel net/mlx5e mlx5e_ptp_open. When kvzalloc_node or kvzalloc fails, memory referenced by c or cparams is not freed. Stable kernel commits fix the error path by freeing the allocated array.

Likely exposure

Exposure appears limited to affected Linux kernels where the mlx5e PTP open path can be reached. The bundle lists Linux kernel versions including 5.11 through 6.5 markers, but provides no CPEs or distribution package mapping.

Exploitation context

The bundle marks KEV as false and provides no public exploit, active exploitation report, or weaponized technique. It describes a reliability/resource-leak flaw, not a confirmed code execution or privilege escalation issue.

Researcher notes

The evidence is narrow: CVE text and stable commit references identify a memory leak and fix location. Missing details include CVSS, CWE, exact distro impact, trigger preconditions, and whether unprivileged users can reach the path.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution advisories for backported fixes and package versions.
  • Prioritize systems using affected kernels with mlx5e networking enabled.
  • Monitor kernel memory pressure until patched.
  • Avoid inventing workarounds; follow vendor kernel guidance.

Validation and detection

  • Inventory Linux kernel versions across managed systems.
  • Identify systems using the mlx5e driver and PTP-related functionality.
  • Compare installed kernels against vendor fixed package guidance.
  • Review change logs for the referenced stable commit identifiers.
  • Confirm patched systems no longer carry the vulnerable code path.
Prepared
Confidence
medium
Sources
6

Public sources used

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-2023-54169 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux145e5637d941daec2e8d1ff21676cbf1aa62cf4d, 145e5637d941daec2e8d1ff21676cbf1aa62cf4d, 145e5637d941daec2e8d1ff21676cbf1aa62cf4d, 145e5637d941daec2e8d1ff21676cbf1aa62cf4dunaffected
LinuxLinux5.11, 0, 5.15.121, 6.1.40, 6.4.5, 6.5affected
Weakness

CWE details

No CWE listed

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