linux-cve-announce - CVE-2025-38530: comedi: pcl812: 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: <2025081655-CVE-2025-38530-1e2d@gregkh>
Date: Sat, 16 Aug 2025 13:14:01 +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-38530: comedi: pcl812: 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: pcl812: Fix bit shift out of bounds

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

	if ((1 << it->options[1]) & board->irq_bits) {

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-38530 to this issue.


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

	Issue introduced in 2.6.30 with commit fcdb427bc7cf5e9e5d7280cf09c08dec49b49432 and fixed in 6.1.147 with commit 5bfa301e1e59a9b1a7b62a800b54852337c97416
	Issue introduced in 2.6.30 with commit fcdb427bc7cf5e9e5d7280cf09c08dec49b49432 and fixed in 6.6.100 with commit 7e470d8efd10725b189ca8951973a8425932398a
	Issue introduced in 2.6.30 with commit fcdb427bc7cf5e9e5d7280cf09c08dec49b49432 and fixed in 6.12.40 with commit a27e27eee313fe1c450b6af1e80e64412546cab4
	Issue introduced in 2.6.30 with commit fcdb427bc7cf5e9e5d7280cf09c08dec49b49432 and fixed in 6.15.8 with commit 16c173abee315953fd17a279352fec4a1faee862
	Issue introduced in 2.6.30 with commit fcdb427bc7cf5e9e5d7280cf09c08dec49b49432 and fixed in 6.16 with commit b14b076ce593f72585412fc7fd3747e03a5e3632

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-38530
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/pcl812.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/5bfa301e1e59a9b1a7b62a800b54852337c97416
	https://git.kernel.org/stable/c/7e470d8efd10725b189ca8951973a8425932398a
	https://git.kernel.org/stable/c/a27e27eee313fe1c450b6af1e80e64412546cab4
	https://git.kernel.org/stable/c/16c173abee315953fd17a279352fec4a1faee862
	https://git.kernel.org/stable/c/b14b076ce593f72585412fc7fd3747e03a5e3632