linux-cve-announce - CVE-2025-22051: staging: gpib: Fix Oops after disconnect in agilent usb

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: <2025041603-CVE-2025-22051-68ac@gregkh>
Date: Wed, 16 Apr 2025 16:12:22 +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-22051: staging: gpib: Fix Oops after disconnect in agilent usb

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

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

staging: gpib: Fix Oops after disconnect in agilent usb

If the agilent usb dongle is disconnected subsequent calls to the
driver cause a NULL dereference Oops as the bus_interface
is set to NULL on disconnect.

This problem was introduced by setting usb_dev from the bus_interface
for dev_xxx messages.

Previously bus_interface was checked for NULL only in the functions
directly calling usb_fill_bulk_urb or usb_control_msg.

Check for valid bus_interface on all interface entry points
and return -ENODEV if it is NULL.

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


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

	Issue introduced in 6.13 with commit fbae7090f30c1bd5a351d0c8f82b6a635718b8d8 and fixed in 6.13.11 with commit e88633705078f40391a9afc6cc8ea3025e6f692b
	Issue introduced in 6.13 with commit fbae7090f30c1bd5a351d0c8f82b6a635718b8d8 and fixed in 6.14.2 with commit 50ef6e45bec79da4c5a01fad4dc23466ba255099
	Issue introduced in 6.13 with commit fbae7090f30c1bd5a351d0c8f82b6a635718b8d8 and fixed in 6.15-rc1 with commit 8491e73a5223acb0a4b4d78c3f8b96aa9c5e774d

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-22051
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/staging/gpib/agilent_82357a/agilent_82357a.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/e88633705078f40391a9afc6cc8ea3025e6f692b
	https://git.kernel.org/stable/c/50ef6e45bec79da4c5a01fad4dc23466ba255099
	https://git.kernel.org/stable/c/8491e73a5223acb0a4b4d78c3f8b96aa9c5e774d