CVE-2023-53267: driver: soc: xilinx: fix memory leak in xlnx_add_cb_for_notify_event()
In the Linux kernel, the following vulnerability has been resolved:
driver: soc: xilinx: fix memory leak in xlnx_add_cb_for_notify_event()
The kfree() should be called when memory fails to be allocated for
cb_data in xlnx_add_cb_for_notify_event(), otherwise there will be
a memory leak, so add kfree() to fix it.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the Xilinx SoC notification callback path. A local low-privileged user could potentially trigger resource exhaustion affecting availability. It is not listed as known exploited in CISA KEV, and the provided sources do not describe remote exploitation or data theft.
Executive priority
Treat as a routine but real availability fix. It is not a remote takeover issue based on provided evidence, but affected shared or embedded Linux systems should receive normal kernel maintenance promptly.
Technical view
The issue is CWE-401 in xlnx_add_cb_for_notify_event(): when allocation for cb_data fails, previously allocated memory was not freed. Kernel stable commits add kfree() on that failure path. CVSS 3.1 is 5.5, with local attack vector, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions where the Xilinx SoC driver code is present or enabled. The source lists Linux 5.19 through fixed stable points including 6.1.18 and 6.2.5, but deployment-specific backports must be checked.
Exploitation context
The source evidence supports local, low-privilege availability risk only. CISA KEV status is false in the bundle, and no cited source claims active exploitation, public exploit availability, remote reachability, confidentiality impact, or integrity impact.
Researcher notes
Evidence is limited to the CVE text, CVSS vector, affected version metadata, and kernel stable commit references. The vulnerable condition is an allocation-failure cleanup bug, so validation should focus on code/package provenance rather than exploit reproduction.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on version numbers.
Restrict unnecessary local user or workload access on affected systems.
If patching is delayed, follow vendor guidance for supported mitigations.
Validation and detection
Inventory deployed Linux kernel versions on Xilinx-related systems.
Confirm whether the Xilinx SoC driver is built, loaded, or required.
Review kernel package changelogs for the referenced stable commits.
Prioritize validation on multi-user or shared workload hosts.
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.