linux-cve-announce - CVE-2025-38482: comedi: das6402: Fix bit shift out of bounds

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: <2025072814-CVE-2025-38482-f4ed@gregkh>
Date: Mon, 28 Jul 2025 13:22:24 +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-38482: comedi: das6402: Fix bit shift out of bounds

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

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

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

comedi: das6402: Fix bit shift out of bounds

When checking for a supported IRQ number, the following test is used:

	/* IRQs 2,3,5,6,7, 10,11,15 are valid for "enhanced" mode */
	if ((1 << it->options[1]) & 0x8cec) {

However, `it->options[i]` is an unchecked `int` value from userspace, so
the shift amount could be negative or out of bounds.  Fix the test by
requiring `it->options[1]` to be within bounds before proceeding with
the original test.  Valid `it->options[1]` values that select the IRQ
will be in the range [1,15]. The value 0 explicitly disables the use of
interrupts.

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


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

	Issue introduced in 3.15 with commit 79e5e6addbb18bf56075f0ff552094a28636dd03 and fixed in 6.1.147 with commit a18a42e77545afcacd6a2b8d9fc16191b87454df
	Issue introduced in 3.15 with commit 79e5e6addbb18bf56075f0ff552094a28636dd03 and fixed in 6.6.100 with commit 8a3637027ceeba4ca5e500b23cb7d24c25592513
	Issue introduced in 3.15 with commit 79e5e6addbb18bf56075f0ff552094a28636dd03 and fixed in 6.12.40 with commit 3eab654f5d199ecd45403c6588cda63e491fcfca
	Issue introduced in 3.15 with commit 79e5e6addbb18bf56075f0ff552094a28636dd03 and fixed in 6.15.8 with commit 4a3c18cde02e35aba87e0ad5672b3e1c72dda5a4
	Issue introduced in 3.15 with commit 79e5e6addbb18bf56075f0ff552094a28636dd03 and fixed in 6.16 with commit 70f2b28b5243df557f51c054c20058ae207baaac

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-38482
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/comedi/drivers/das6402.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/a18a42e77545afcacd6a2b8d9fc16191b87454df
	https://git.kernel.org/stable/c/8a3637027ceeba4ca5e500b23cb7d24c25592513
	https://git.kernel.org/stable/c/3eab654f5d199ecd45403c6588cda63e491fcfca
	https://git.kernel.org/stable/c/4a3c18cde02e35aba87e0ad5672b3e1c72dda5a4
	https://git.kernel.org/stable/c/70f2b28b5243df557f51c054c20058ae207baaac