CVE-2023-54315 json
powerpc/powernv/sriov: perform null check on iov before dereferencing iov
published 10mo ago modified 4mo ago also EUVD-2023-60489
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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; ^
Patch / fix
- Linux Linux 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5
- linux Debian 12 6.1.52-1
- linux Debian 14, Debian 13 6.4.4-1
debian advisories DEBIAN-CVE-2023-54315
- linux Ubuntu 22.04 LTS 5.15.0-86.96
- linux-aws Ubuntu 22.04 LTS 5.15.0-1047.52
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1044.52
- linux-gke Ubuntu 22.04 LTS 5.15.0-1044.49
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1040.43
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1044.49
- linux-azure Ubuntu 22.04 LTS 5.15.0-1049.56
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1030.35
ubuntu advisories UBUNTU-CVE-2023-54315
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.194.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.194.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +3 more 5.14.21-150400.24.194.1.150400.24.98.3
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:0617-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0411-1
- git.kernel.org/stable/c/07c19c0ad4b07f4b598da369714de028f6a6a323 commit
- git.kernel.org/stable/c/d3a0d96c16e5f8d55e2c70163abda3c7c8328106 commit
- git.kernel.org/stable/c/d9a1aaea856002cb58dfb7c8d8770400fa1a0299 commit
- git.kernel.org/stable/c/6314465b88072a6b6f3b3c12a7898abe09095f95 commit
- git.kernel.org/stable/c/72990144e17e5e2cb378f1d9b10530b85b9bc382 commit
- git.kernel.org/stable/c/f4f913c980bc6abe0ccfe88fe3909c125afe4a2d commit
Is CVE-2023-54315 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54315 updated cvss 3.3
kernel: powerpc/powernv/sriov: perform null check on iov before dereferencing iov
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-16).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/07c19c0ad4b07f4b598da369714de028f6a6a323
- git.kernel.org /stable/c/d3a0d96c16e5f8d55e2c70163abda3c7c8328106
- git.kernel.org /stable/c/d9a1aaea856002cb58dfb7c8d8770400fa1a0299
- git.kernel.org /stable/c/6314465b88072a6b6f3b3c12a7898abe09095f95
- git.kernel.org /stable/c/72990144e17e5e2cb378f1d9b10530b85b9bc382
- git.kernel.org /stable/c/f4f913c980bc6abe0ccfe88fe3909c125afe4a2d
Sources
- CVE List CVE-2023-54315
- NVD CVE-2023-54315
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.