In the Linux kernel, the following vulnerability has been resolved:
accel/qaic: Fix slicing memory leak
The temporary buffer storing slicing configuration data from user is only
freed on error. This is a memory leak. Free the buffer unconditionally.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53350 is a Linux kernel memory leak in the accel/qaic driver. A local authenticated user could potentially consume kernel memory and affect system availability. The sources do not indicate data theft, integrity impact, remote access, or active exploitation.
Executive priority
Handle through normal vulnerability management, with faster action for shared Linux systems or accelerator hosts. Business urgency is availability-driven: a local user may be able to degrade service reliability, but sources do not support remote compromise or active exploitation.
Technical view
The qaic driver failed to free a temporary user-provided slicing configuration buffer on the success path. The fix frees the buffer unconditionally. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact only.
Likely exposure
Exposure is most likely on Linux systems running affected 6.4-era kernel builds where the accel/qaic driver is present or enabled. Systems without this driver or with vendor kernels containing the referenced stable fixes are less likely exposed.
Exploitation context
The CVSS vector requires local, low-privileged access. The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation or public weaponization. Treat this as a local denial-of-service risk, not a remote compromise issue.
Researcher notes
This is CWE-401 memory leak behavior in the kernel qaic slicing path. Analysis should focus on whether downstream vendor kernels include the stable fixes and whether qaic code is reachable on deployed hosts. Evidence is limited to CVE data and kernel fix references.
Mitigation direction
Apply Linux kernel or distribution updates containing the referenced stable fixes.
Prioritize systems where accel/qaic hardware or the qaic driver is enabled.
If updates are unavailable, follow vendor guidance for driver disablement or risk reduction.
Reduce unnecessary local user access on affected accelerator hosts.
Track distribution advisories for backported fixes and package status.
Validation and detection
Inventory Linux hosts using affected 6.4-era kernel packages.
Confirm whether the accel/qaic driver is built, installed, or loaded.
Verify vendor kernel changelogs include the referenced stable commits.
Check asset exposure against systems with local multi-user access.
Document any compensating controls for hosts awaiting patches.
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.
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.
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.
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.