# CVE-2023-53787: regulator: da9063: fix null pointer deref with partial DT config

> A null pointer dereference in the Linux kernel da9063 regulator driver causes a system crash during boot if device tree configuration is incomplete.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-53787, DEBIAN-CVE-2023-53787, GHSA-9f5w-rgmf-x5m7, UBUNTU-CVE-2023-53787

## What is CVE-2023-53787?

CVE-2023-53787 is a vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

regulator: da9063: fix null pointer deref with partial DT config

When some of the da9063 regulators do not have corresponding DT nodes
a null pointer dereference occurs on boot because such regulators have
no init_data causing the pointers calculated in
da9063_check_xvp_constraints() to be invalid.

Do not dereference them in this case.

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


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

Apply the vendor's patch.

## Is CVE-2023-53787 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53787 is a vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53787 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-53787/ (Markdown: https://insights.sbomify.com/CVE-2023-53787/index.md)
```

## Sources

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

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