LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53367: accel/habanalabs: fix mem leak in capture user mappings

In the Linux kernel, the following vulnerability has been resolved: accel/habanalabs: fix mem leak in capture user mappings This commit fixes a memory leak caused when clearing the user_mappings info when a new context is opened immediately after user_mapping is captured and a hard reset is performed.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-53367 is a Linux kernel memory leak in the accel/habanalabs driver. A local authenticated user could trigger availability impact, potentially causing resource exhaustion. The source bundle does not show data theft, integrity impact, or confirmed active exploitation.

Executive priority

Treat this as a targeted availability risk, not a broad remote compromise. Patch during normal kernel maintenance, faster where shared or multi-tenant systems expose affected accelerator resources to local users.

Technical view

The issue is CWE-401 in Linux accel/habanalabs user mapping handling. A leak occurs when user_mappings information is cleared after a captured user mapping, followed by a hard reset and immediate new context creation. CVSS 3.1 is 5.5: local, low complexity, low privileges, no user interaction, high availability impact only.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the habanalabs accelerator driver present and reachable by local users or workloads. The bundle does not map affected versions to specific distribution packages or appliances.

Exploitation context

The CVSS vector requires local access and low privileges. The CVE is not listed as KEV in the bundle, and no cited source reports active exploitation or public weaponization.

Researcher notes

Evidence supports a local availability-only memory leak in a specific Linux kernel driver path. The bundle provides stable fix commits but no exploit indicators, distro package mapping, or proof-of-concept details. Avoid assuming exposure without confirming driver presence and affected kernel lineage.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Check Linux distribution security advisories for exact fixed package versions.
  • Prioritize systems using habanalabs accelerator hardware or driver paths.
  • Restrict local access to systems where untrusted users can run workloads.
  • If unused, consider disabling the affected driver per vendor guidance.

Validation and detection

  • Inventory kernels against vendor advisories and the CVE affected-version data.
  • Verify fixed builds include the referenced stable kernel commits.
  • Identify systems with habanalabs accelerator support enabled or loaded.
  • Review local-user and workload access on exposed compute hosts.
  • Monitor vendor updates for package-level fixed-version mapping.
Prepared
Confidence
high
Sources
4

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-53367 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
3Source 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-53367Attack 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
LinuxLinux0feaf86d4e69507ab9b2af7dcc63a6886352d5db, 0feaf86d4e69507ab9b2af7dcc63a6886352d5dbunaffected
LinuxLinux5.1, 0, 6.4.12, 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.