linux-cve-announce - CVE-2025-38613: staging: gpib: fix unset padding field copy back to userspace

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: <2025081924-CVE-2025-38613-8505@gregkh>
Date: Tue, 19 Aug 2025 19:18:59 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38613: staging: gpib: fix unset padding field copy back to userspace

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

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

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

staging: gpib: fix unset padding field copy back to userspace

The introduction of a padding field in the gpib_board_info_ioctl is
showing up as initialized data on the stack frame being copyied back
to userspace in function board_info_ioctl. The simplest fix is to
initialize the entire struct to zero to ensure all unassigned padding
fields are zero'd before being copied back to userspace.

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


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

	Issue introduced in 6.13 with commit 9dde4559e93955ccc47d588f7fd051684d55c4e7 and fixed in 6.16.1 with commit 19dedd4f70f5a6505e7c601ef7dd40542d1d9aa5
	Issue introduced in 6.13 with commit 9dde4559e93955ccc47d588f7fd051684d55c4e7 and fixed in 6.17-rc1 with commit a739d3b13bff0dfa1aec679d08c7062131a2a425

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-38613
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/common/gpib_os.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/19dedd4f70f5a6505e7c601ef7dd40542d1d9aa5
	https://git.kernel.org/stable/c/a739d3b13bff0dfa1aec679d08c7062131a2a425