linux-cve-announce - CVE-2025-22092: PCI: Fix NULL dereference in SR-IOV VF creation error path

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: <2025041617-CVE-2025-22092-e56b@gregkh>
Date: Wed, 16 Apr 2025 16:13:03 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22092: PCI: Fix NULL dereference in SR-IOV VF creation error path

Description
===========

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

PCI: Fix NULL dereference in SR-IOV VF creation error path

Clean up when virtfn setup fails to prevent NULL pointer dereference
during device removal. The kernel oops below occurred due to incorrect
error handling flow when pci_setup_device() fails.

Add pci_iov_scan_device(), which handles virtfn allocation and setup and
cleans up if pci_setup_device() fails, so pci_iov_add_virtfn() doesn't need
to call pci_stop_and_remove_bus_device().  This prevents accessing
partially initialized virtfn devices during removal.

  BUG: kernel NULL pointer dereference, address: 00000000000000d0
  RIP: 0010:device_del+0x3d/0x3d0
  Call Trace:
   pci_remove_bus_device+0x7c/0x100
   pci_iov_add_virtfn+0xfa/0x200
   sriov_enable+0x208/0x420
   mlx5_core_sriov_configure+0x6a/0x160 [mlx5_core]
   sriov_numvfs_store+0xae/0x1a0

[bhelgaas: commit log, return ERR_PTR(-ENOMEM) directly]

The Linux kernel CVE team has assigned CVE-2025-22092 to this issue.


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

	Issue introduced in 6.13 with commit e3f30d563a388220a7c4e3b9a7b52ac0b0324b26 and fixed in 6.13.11 with commit ef421b4d206f0d3681804b8f94f06a8458a53aaf
	Issue introduced in 6.13 with commit e3f30d563a388220a7c4e3b9a7b52ac0b0324b26 and fixed in 6.14.2 with commit c67a233834b778b8c78f8b62c072ccf87a9eb6d0
	Issue introduced in 6.13 with commit e3f30d563a388220a7c4e3b9a7b52ac0b0324b26 and fixed in 6.15-rc1 with commit 04d50d953ab46d96b0b32d5ad955fceaa28622db

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-2025-22092
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:
	drivers/pci/iov.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/ef421b4d206f0d3681804b8f94f06a8458a53aaf
	https://git.kernel.org/stable/c/c67a233834b778b8c78f8b62c072ccf87a9eb6d0
	https://git.kernel.org/stable/c/04d50d953ab46d96b0b32d5ad955fceaa28622db