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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025123037-CVE-2023-54315-7005@gregkh>
Date: Tue, 30 Dec 2025 13:24:08 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54315: powerpc/powernv/sriov: perform null check on iov before dereferencing iov

From: Greg Kroah-Hartman <gregkh@...nel.org>

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;
           ^

The Linux kernel CVE team has assigned CVE-2023-54315 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.9 with commit 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and fixed in 5.10.188 with commit 07c19c0ad4b07f4b598da369714de028f6a6a323
	Issue introduced in 5.9 with commit 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and fixed in 5.15.121 with commit d3a0d96c16e5f8d55e2c70163abda3c7c8328106
	Issue introduced in 5.9 with commit 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and fixed in 6.1.39 with commit d9a1aaea856002cb58dfb7c8d8770400fa1a0299
	Issue introduced in 5.9 with commit 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and fixed in 6.3.13 with commit 6314465b88072a6b6f3b3c12a7898abe09095f95
	Issue introduced in 5.9 with commit 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and fixed in 6.4.4 with commit 72990144e17e5e2cb378f1d9b10530b85b9bc382
	Issue introduced in 5.9 with commit 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and fixed in 6.5 with commit f4f913c980bc6abe0ccfe88fe3909c125afe4a2d

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-54315
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	arch/powerpc/platforms/powernv/pci-sriov.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/07c19c0ad4b07f4b598da369714de028f6a6a323
	https://git.kernel.org/stable/c/d3a0d96c16e5f8d55e2c70163abda3c7c8328106
	https://git.kernel.org/stable/c/d9a1aaea856002cb58dfb7c8d8770400fa1a0299
	https://git.kernel.org/stable/c/6314465b88072a6b6f3b3c12a7898abe09095f95
	https://git.kernel.org/stable/c/72990144e17e5e2cb378f1d9b10530b85b9bc382
	https://git.kernel.org/stable/c/f4f913c980bc6abe0ccfe88fe3909c125afe4a2d