Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability issue in AMDGPU self-test cleanup. A memory leak can occur because MES queue fences were not freed during ring shutdown. The recorded impact is denial of service, not data theft or tampering. Evidence provided does not show active exploitation.
Executive priority
Treat this as a moderate patch-management item. It is not currently evidenced as exploited, but it can affect availability on relevant Linux systems and should be addressed through normal kernel update cycles.
Technical view
CVE-2023-53370 is CWE-401 in Linux drm/amdgpu. The fix frees fences associated with MES queues during amdgpu_ring_fini. CVSS 3.1 is 5.5: local access, low complexity, low privileges, no user interaction, unchanged scope, high availability impact only.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds with the amdgpu driver code path. The bundle lists Linux as affected and references stable kernel fixes, but does not define environmental prerequisites beyond the local attack vector.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates exploitation is local and requires low privileges, with no confidentiality or integrity impact recorded.
Researcher notes
The available evidence is limited to the CVE record, CVSS metadata, CWE-401 classification, and upstream stable commit references. The bundle does not provide proof-of-concept details, observed exploitation, or a complete distribution-specific affected matrix.
Mitigation direction
- Apply vendor kernel updates that include the referenced stable fixes.
- Confirm distribution backports rather than relying only on upstream version numbers.
- Prioritize shared Linux hosts where untrusted local users can run workloads.
- Monitor vendor advisories for any clarified affected-version ranges.
- Use standard change controls for kernel update testing and rollout.
Validation and detection
- Inventory Linux kernel versions across AMDGPU-capable systems.
- Check vendor advisories for CVE-2023-53370 backport status.
- Confirm whether deployed kernels include the referenced stable commits.
- Review asset exposure where local users or tenants have shell access.
- Track availability symptoms separately from exploitation claims.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2023-53370 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/ce3288d8d654b252ba832626e7de481c195ef20aCVE reference, Linux
- https://git.kernel.org/stable/c/8d8c96efcec95736622381b2afc0fe9e317f88aaCVE reference, Linux
- https://git.kernel.org/stable/c/31d7c3a4fc3d312a0646990767647925d5bde540CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.