LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53674: clk: Fix memory leak in devm_clk_notifier_register()

In the Linux kernel, the following vulnerability has been resolved: clk: Fix memory leak in devm_clk_notifier_register() devm_clk_notifier_register() allocates a devres resource for clk notifier but didn't register that to the device, so the notifier didn't get unregistered on device detach and the allocated resource was leaked. Fix the issue by registering the resource through devres_add(). This issue was found with kmemleak on a Chromebook.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53674 is a Linux kernel memory leak in clock notifier cleanup. A resource was allocated but not attached to device-managed cleanup, so detach could leave the notifier registered and memory leaked. Sources do not provide CVSS, CWE, or exploit evidence.

Executive priority

Treat this as a routine kernel maintenance item unless vendors identify broader impact. Current sources indicate a memory leak, not confirmed compromise or active exploitation. Keep patching aligned with normal kernel update cycles.

Technical view

In devm_clk_notifier_register(), a devres resource for a clock notifier was allocated but not registered with the device. On device detach, cleanup did not unregister the notifier, leaking the allocation. Kernel stable commits fix this by adding the missing devres_add() registration.

Likely exposure

Exposure depends on Linux kernels containing the vulnerable clock framework code and drivers using devm_clk_notifier_register(). The source bundle lists Linux as affected, but version range details are incomplete and should be verified against vendor kernel packages.

Exploitation context

The bundle states the issue was found with kmemleak on a Chromebook. It does not cite active exploitation, KEV listing, public exploit code, remote attack paths, privilege escalation, or data disclosure.

Researcher notes

Evidence is narrow: upstream description, stable commit references, and no CVSS. Focus analysis on affected kernel branches, downstream backports, and reachable driver paths using devm_clk_notifier_register(). Avoid assuming exploitability beyond resource leakage.

Mitigation direction

  • Review Linux vendor advisories for CVE-2023-53674 and affected kernel builds.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize systems with frequent device attach or detach activity.
  • Track downstream distribution backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions and vendor package revisions across managed assets.
  • Check whether vendor advisories map local kernels to CVE-2023-53674 fixes.
  • Confirm patched kernels include the devres_add() clock notifier fix.
  • Monitor kernel logs and memory-leak diagnostics where device detach is common.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

cve · low confidence lookup

CVE-2023-53674 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6d30d50d037dfa092f9d5d1fffa348ab4abb7163, 6d30d50d037dfa092f9d5d1fffa348ab4abb7163, 6d30d50d037dfa092f9d5d1fffa348ab4abb7163, 6d30d50d037dfa092f9d5d1fffa348ab4abb7163, 6d30d50d037dfa092f9d5d1fffa348ab4abb7163unaffected
LinuxLinux5.11, 0, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.