CVE-2023-54221: clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 280a5ff665e12d1e0c54c20cedc9c5008aa686a5, d17c16a2b2a6589c45b0bfb1b9914da80b72d89e, e02ba11b457647050cb16e7cad16cec3c252fade.
Low priority for now. Upgrade to Linux Linux 280a5ff665e12d1e0c54c20cedc9c5008aa686a5, d17c16a2b2a6589c45b0bfb1b9914da80b72d89e, e02ba11b457647050cb16e7cad16cec3c252fade or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe In function probe(), it returns directly without unregistered hws when error occurs. Fix this by adding 'goto unregister_hws;' on line 295 and line 310. Use devm_kzalloc() instead of kzalloc() to automatically free the memory using devm_kfree() when error occurs. Replace of_iomap() with devm_of_iomap() to automatically handle the unused ioremap region and delete 'iounmap(anatop_base);' in unregister_hws.
- Published
- Dec 30, 2025
- Updated
- Oct 28, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- 24defbe194b650218680fcd9dec8cd103537b531 and later · before 280a5ff665e12d1e0c54c20cedc9c5008aa686a5affected · git
- 24defbe194b650218680fcd9dec8cd103537b531 and later · before fac9c624138c4bc021d7a8ee3b974c9e10926d92affected · git
- 24defbe194b650218680fcd9dec8cd103537b531 and later · before d17c16a2b2a6589c45b0bfb1b9914da80b72d89eaffected · git
- 24defbe194b650218680fcd9dec8cd103537b531 and later · before e02ba11b457647050cb16e7cad16cec3c252fadeaffected · git
- before 5.18not affected · semver
- 6.1.39 and later · up to and including 6.1.*not affected · semver
- 6.3.13 and later · up to and including 6.3.*not affected · semver
- 6.4.4 and later · up to and including 6.4.*not affected · semver
- 6.5 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.4-1 | 6.4.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54219Dec 30, 2025 · Revert "IB/isert: Fix incorrect release of isert connection"30Monitor
- ← EarlierCVE-2023-54220Dec 30, 2025 · serial: 8250: Fix oops for port->pm on uart_change_pm()31Monitor
- Later →CVE-2023-54222Dec 30, 2025 · hte: tegra-194: Fix off by one in tegra_hte_map_to_line_id()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 280a5ff665e12d1e0c54c20cedc9c5008aa686a5 | Vendor (CNA) |
| Linux Linux | d17c16a2b2a6589c45b0bfb1b9914da80b72d89e | Vendor (CNA) |
| Linux Linux | e02ba11b457647050cb16e7cad16cec3c252fade | Vendor (CNA) |
| Linux Linux | fac9c624138c4bc021d7a8ee3b974c9e10926d92 | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.