Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a memory leak in MediaTek clock-driver error handling. A local low-privileged user could contribute to availability impact on affected systems, but the supplied sources do not show data theft, integrity impact, or active exploitation.
Executive priority
Treat as a moderate kernel maintenance item. It can affect availability, but available evidence points to local exploitation conditions and no confirmed active exploitation. Prioritize affected MediaTek systems and fold into normal kernel patch cycles.
Technical view
In drivers/clk/mediatek/clk-mtk.c, mtk_clk_simple_probe() did not release an of_iomap() mapping when clk_data was missing on an error path. The issue is tracked as CWE-401 and fixed by adding base release handling in stable Linux commits.
Likely exposure
Likely exposure is Linux systems running affected kernel versions or builds that include MediaTek clock support and the vulnerable probe path. MediaTek-based devices are more relevant than generic systems without that driver or hardware path.
Exploitation context
The CVSS vector is local, low complexity, low privileges required, no user interaction, and high availability impact. The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation.
Researcher notes
Evidence is limited to the CVE record and Linux stable references. The described bug is an error-path resource leak found by Smatch and also observed in linux-next. No exploit details, real-world abuse, or non-Linux affected products are provided.
Mitigation direction
- Apply the relevant Linux stable fix or vendor kernel update.
- Prioritize MediaTek-based devices and kernels with MediaTek clock support.
- Track distribution advisories for backported kernel fixes.
- If no vendor package is available, consult vendor guidance before changing kernels.
Validation and detection
- Inventory kernel versions against the affected version data.
- Confirm whether MediaTek clock driver support is present in builds.
- Review whether the stable fix is included or backported.
- Validate scanners map the running kernel build to this CVE.
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-53424 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/847d5dd788ce05f0aaaa36ea174f7f0b9cf86f7dCVE reference, Linux
- https://git.kernel.org/stable/c/2cae6a28d8c12c597e8656962271520434c61c48CVE reference, Linux
- https://git.kernel.org/stable/c/47234e19b00816a8a7b278c7173f6d4e928c43c7CVE reference, Linux
- https://git.kernel.org/stable/c/3db7285e044144fd88a356f5b641b9cd4b231a77CVE 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.