| 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
| ||
|
Message-ID: <2025090546-CVE-2025-39685-ddff@gregkh> Date: Fri, 5 Sep 2025 19:20: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-39685: comedi: pcl726: Prevent invalid irq number From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: comedi: pcl726: Prevent invalid irq number The reproducer passed in an irq number(0x80008000) that was too large, which triggered the oob. Added an interrupt number check to prevent users from passing in an irq number that was too large. If `it->options[1]` is 31, then `1 << it->options[1]` is still invalid because it shifts a 1-bit into the sign bit (which is UB in C). Possible solutions include reducing the upper bound on the `it->options[1]` value to 30 or lower, or using `1U << it->options[1]`. The old code would just not attempt to request the IRQ if the `options[1]` value were invalid. And it would still configure the device without interrupts even if the call to `request_irq` returned an error. So it would be better to combine this test with the test below. The Linux kernel CVE team has assigned CVE-2025-39685 to this issue. Affected and fixed versions =========================== Issue introduced in 3.13 with commit fff46207245cd9e39c05b638afaee2478e64914b and fixed in 5.15.190 with commit bab220b0bb5af652007e278e8e8357f952b0e1ea Issue introduced in 3.13 with commit fff46207245cd9e39c05b638afaee2478e64914b and fixed in 6.1.149 with commit 5a33d07c94ba91306093e823112a7aa9727549f6 Issue introduced in 3.13 with commit fff46207245cd9e39c05b638afaee2478e64914b and fixed in 6.6.103 with commit 0eb4ed2aa261dee228f1668dbfa6d87353e8162d Issue introduced in 3.13 with commit fff46207245cd9e39c05b638afaee2478e64914b and fixed in 6.12.44 with commit a3cfcd0c78c80ca7cd80372dc28f77d01be57bf6 Issue introduced in 3.13 with commit fff46207245cd9e39c05b638afaee2478e64914b and fixed in 6.16.4 with commit d8992c9a01f81128f36acb7c5755530e21fcd059 Issue introduced in 3.13 with commit fff46207245cd9e39c05b638afaee2478e64914b and fixed in 6.17-rc3 with commit 96cb948408b3adb69df7e451ba7da9d21f814d00 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-39685 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/pcl726.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/bab220b0bb5af652007e278e8e8357f952b0e1ea https://git.kernel.org/stable/c/5a33d07c94ba91306093e823112a7aa9727549f6 https://git.kernel.org/stable/c/0eb4ed2aa261dee228f1668dbfa6d87353e8162d https://git.kernel.org/stable/c/a3cfcd0c78c80ca7cd80372dc28f77d01be57bf6 https://git.kernel.org/stable/c/d8992c9a01f81128f36acb7c5755530e21fcd059 https://git.kernel.org/stable/c/96cb948408b3adb69df7e451ba7da9d21f814d00
Powered by blists - more mailing lists