Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795056124; b=y/KhQ71vbvy5WVcFDaKkFNpCkTXVV2ZLJgm49fhMFsMZ2UEAlrsGZ38lGc9It6tUbumU zCp1LvKdEzXyL92C1eFuI1urFU6YmfoWlCbRrsQkg0dEoSNi1nj80OPq0p75QIAinSLUj aZ6sd4rctw6dOby+phN/ZLHBx9xVD9ZYyAoAaJi+iLhubpo5IGbg3/QIPpY2qafS+qBnJ dA5y2G6rSVn4vYZp3zJQeWGLhuEzjh9YQnkax5UfONrAU7+m4vSYsCMttXFduvY8KN6zC DWN8w3pTfoM+xHAI3JJHgsJF4dfhxbYbiQin9CGwyu77WNGaqd6hvC5nYHjtt6ZzHdQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795056124; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=InRRiHvsal56kh3t1W9RQQvKQJzfd9tdY5iDf7BD6Io=; b=NIJfQPXD2540tDxCzCtfAKcg5WoEq7riqX2M8/44LO3i+FBwe+Oi769D+HHIIP+imzhQ NELBtIEPHaDwX5Y1zkAQv4ASFj6PqlflbliF8MG8epOL88AcFEyIhs1HuPuOmabyyKdLX fe4nM4J0SC6Uta+aQF4V7cO3vHMHmj2XE1Ibzo7LnqXimEHCST61CQAXD154TOAyYJ72/ 20GUJ5O6pQV/0bMCqpZi004abxbyStc/nNirTM+Sb1L+c5F+9rI2DhmC6Sgl2wWSafGCJ QQVQCXSKg/kwWHUVUa0lmdrdsBfJJDw/BPa7Nohil2LMhy39rG+k9rlXmBGtFGCF+eQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zQOyqOpg; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7A432606A31C; Thu, 19 Nov 2026 02:42:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zQOyqOpg Received: by smtp.kernel.org (Postfix) with ESMTPSA id D35551F000C4; Thu, 19 Nov 2026 02:42:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795056124; bh=InRRiHvsal56kh3t1W9RQQvKQJzfd9tdY5iDf7BD6Io=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=zQOyqOpgLFTJdE4lqTgcRHgH8RNR7YkVSvwb8XGntVgyRrjFRPRLHoF4e8FePqJq5 EQLjXbbSevZPsQbDq5dzDh4VSWiW8cO7MMNBeoegzkmv87IjIdIxDB3Zn8Hw2E5xFn G19/wf24W28zoSLYlSiTHJLWLJG7TMHOo1p9opIQ= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Yogesh Gaur , Sasha Levin Subject: [PATCH 5.15 1876/2214] comedi: pcmuio: validate the IRQs supplied by userspace Date: Wed, 18 Nov 2026 15:59:12 +0100 Message-ID: <20261118150126.317479053@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261118150009.797899913@linuxfoundation.org> References: <20261118150009.797899913@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: patches@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 5.15-stable review patch. If anyone has any objections, please let me know. ------------------ From: Yogesh Gaur [ Upstream commit 9c325b21bba99e597771137fc11b9427c86618d8 ] comedi boards are configured through the COMEDI_DEVCONFIG ioctl, so it->options[1] is a number chosen by userspace. pcmuio passes it to request_irq() without checking it first, which lets an interrupt owned by another irqdomain -- a PCI device's IO-APIC GSI, for instance -- be claimed for this board. When the owner of that interrupt is later released the descriptor is freed while this driver's handler is still installed on it. Every interrupt this board can assert is a legacy ISA one, so the ISA range is the right bound; it is also sufficient, because mp_chip_data->isa_irq is set only by alloc_isa_irq_from_domain() and mp_unmap_irq() returns early when it is set. Bound the value before requesting it, as das16m1.c already does. An out-of-range value is ignored rather than rejected, so the board still attaches without interrupt support, exactly as it does today when request_irq() fails. This board takes two interrupts, one per ASIC, so options[1] and options[2] both need the check. The existing options[2] == dev->irq case is left alone: it covers both ASICs sharing one interrupt and neither having one, and by then options[1] has already been validated. Fixes: 6baef150380d ("Staging: comedi: add pcmmio and pcmuio drivers") Assisted-by: LLM Signed-off-by: Yogesh Gaur Link: https://patch.msgid.link/20260909104848.1763-7-yogeshgaur.83@gmail.com Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin --- drivers/comedi/drivers/pcmuio.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/comedi/drivers/pcmuio.c b/drivers/comedi/drivers/pcmuio.c index ae12a70534151..9e3af643e8c44 100644 --- a/drivers/comedi/drivers/pcmuio.c +++ b/drivers/comedi/drivers/pcmuio.c @@ -546,7 +546,8 @@ static int pcmuio_attach(struct comedi_device *dev, struct comedi_devconfig *it) pcmuio_reset(dev); - if (it->options[1]) { + /* only ISA interrupts are valid on this board */ + if (it->options[1] >= 1 && it->options[1] <= 15) { /* request the irq for the 1st asic */ ret = request_irq(it->options[1], pcmuio_interrupt, 0, dev->board_name, dev); @@ -558,7 +559,7 @@ static int pcmuio_attach(struct comedi_device *dev, struct comedi_devconfig *it) if (it->options[2] == dev->irq) { /* the same irq (or none) is used by both asics */ devpriv->irq2 = it->options[2]; - } else if (it->options[2]) { + } else if (it->options[2] >= 1 && it->options[2] <= 15) { /* request the irq for the 2nd asic */ ret = request_irq(it->options[2], pcmuio_interrupt, 0, dev->board_name, dev); -- 2.53.0