# CVE-2023-54087: ubi: Fix possible null-ptr-deref in ubi_free_volume()

> A null pointer dereference in the Linux kernel UBI subsystem allows local attackers to cause a denial of service via improper error handling during volume addition.

- **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:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54087, DEBIAN-CVE-2023-54087, GHSA-9w7w-3xjc-3wgw, UBUNTU-CVE-2023-54087

## What is CVE-2023-54087?

CVE-2023-54087 is a vulnerability in Linux, published on 24 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:

ubi: Fix possible null-ptr-deref in ubi_free_volume()

It willl cause null-ptr-deref in the following case:

uif_init()
  ubi_add_volume()
    cdev_add() -> if it fails, call kill_volumes()
    device_register()

kill_volumes() -> if ubi_add_volume() fails call this function
  ubi_free_volume()
    cdev_del()
    device_unregister() -> trying to delete a not added device,
			   it causes null-ptr-deref

So in ubi_free_volume(), it delete devices whether they are added
or not, it will causes null-ptr-deref.

Handle the error case whlie calling ubi_add_volume() to fix this
problem. If add volume fails, set the corresponding vol to null,
so it can not be accessed in kill_volumes() and release the
resource in ubi_add_volume() error path.

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


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

Apply the vendor's patch.

## Is CVE-2023-54087 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54087 is a vulnerability in Linux, published on 24 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-54087 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-54087/ (Markdown: https://insights.sbomify.com/CVE-2023-54087/index.md)
```

## Sources

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

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