# CVE-2023-54228: regulator: raa215300: Fix resource leak in case of error

> A resource leak in the Linux kernel regulator driver allows attackers to cause a denial of service by triggering error paths that fail to free memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54228, DEBIAN-CVE-2023-54228, GHSA-q47m-cv74-3xj8, UBUNTU-CVE-2023-54228

## What is CVE-2023-54228?

CVE-2023-54228 is a denial of service vulnerability in Linux, published on 30 Dec 2025. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

regulator: raa215300: Fix resource leak in case of error

The clk_register_clkdev() allocates memory by calling vclkdev_alloc() and
this memory is not freed in the error path. Similarly, resources allocated
by clk_register_fixed_rate() are not freed in the error path.

Fix these issues by using devm_clk_hw_register_fixed_rate() and
devm_clk_hw_register_clkdev().

After this, the static variable clk is not needed. Replace it with 
local variable hw in probe() and drop calling clk_unregister_fixed_rate()
from raa215300_rtc_unregister_device().

## Which versions are affected by CVE-2023-54228?


## How do I fix CVE-2023-54228?

Apply the vendor's patch.

## Is CVE-2023-54228 being exploited?

There is no known exploitation of CVE-2023-54228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54228 and fix it if it is affected.

What it is: CVE-2023-54228 is a denial of service vulnerability in Linux, published on 30 Dec 2025. 
Exploitation: There is no known exploitation of CVE-2023-54228 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54228/ (Markdown: https://insights.sbomify.com/CVE-2023-54228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54228
- OSV: https://osv.dev/vulnerability/CVE-2023-54228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54228/
Summaries are generated and may contain mistakes; the official description above is the record.