# CVE-2023-54315: powerpc/powernv/sriov: perform null check on iov before dereferencing iov

> A null pointer dereference in the Linux kernel's PowerNV SRIOV driver allows local attackers to cause a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54315, DEBIAN-CVE-2023-54315, GHSA-jx25-4v2r-83c2, UBUNTU-CVE-2023-54315

## What is CVE-2023-54315?

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

powerpc/powernv/sriov: perform null check on iov before dereferencing iov

Currently pointer iov is being dereferenced before the null check of iov
which can lead to null pointer dereference errors. Fix this by moving the
iov null check before the dereferencing.

Detected using cppcheck static analysis:
linux/arch/powerpc/platforms/powernv/pci-sriov.c:597:12: warning: Either
the condition '!iov' is redundant or there is possible null pointer
dereference: iov. [nullPointerRedundantCheck]
 num_vfs = iov->num_vfs;
           ^

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


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

Apply the vendor's patch.

## Is CVE-2023-54315 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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