CVE-2023-54221

Kernel memory leak via incomplete probe cleanup

Published Dec 30, 2025 · Updated Dec 30, 2025

Resource-management error in the Linux kernel allows attackers to leak memory during failed i.MX93 clock-controller probing. The imx93_clocks_probe error paths return without unregistering clock hardware, while unmanaged allocation and mapping leave resources unreleased. Reachability requires the i.MX93 clock driver to encounter a probe error; Linux has not published an attacker-controlled trigger or a resulting service interruption.

CVSS severityUnavailable
Unscored
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource-management error in the Linux kernel allows attackers to leak memory during failed i.MX93 clock-controller probing. The imx93_clocks_probe error paths return without unregistering clock hardware, while unmanaged allocation and mapping leave resources unreleased. Reachability requires the i.MX93 clock driver to encounter a probe error; Linux has not published an attacker-controlled trigger or a resulting service interruption.

The record

CVE
CVE-2023-54221
Published
Dec 30, 2025
Updated
Dec 30, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Dec 30, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=24defbe194b650218680fcd9dec8cd103537b531 <280a5ff665e12d1e0c54c20cedc9c5008aa686a5
  2. Affected versionversion=24defbe194b650218680fcd9dec8cd103537b531 <d17c16a2b2a6589c45b0bfb1b9914da80b72d89e
  3. Affected versionversion=24defbe194b650218680fcd9dec8cd103537b531 <e02ba11b457647050cb16e7cad16cec3c252fade
  4. Affected versionversion=24defbe194b650218680fcd9dec8cd103537b531 <fac9c624138c4bc021d7a8ee3b974c9e10926d92
  5. Affected versionversion=5.18

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=24defbe194b650218680fcd9dec8cd103537b531 <280a5ff665e12d1e0c54c20cedc9c5008aa686a5; version=24defbe194b650218680fcd9dec8cd103537b531 <d17c16a2b2a6589c45b0bfb1b9914da80b72d89e; version=24defbe194b650218680fcd9dec8cd103537b531 <e02ba11b457647050cb16e7cad16cec3c252fade; version=24defbe194b650218680fcd9dec8cd103537b531 <fac9c624138c4bc021d7a8ee3b974c9e10926d92; version=5.18

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo