| 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: <2025071010-CVE-2025-38286-eab7@gregkh> Date: Thu, 10 Jul 2025 09:42:27 +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-38286: pinctrl: at91: Fix possible out-of-boundary access From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: pinctrl: at91: Fix possible out-of-boundary access at91_gpio_probe() doesn't check that given OF alias is not available or something went wrong when trying to get it. This might have consequences when accessing gpio_chips array with that value as an index. Note, that BUG() can be compiled out and hence won't actually perform the required checks. The Linux kernel CVE team has assigned CVE-2025-38286 to this issue. Affected and fixed versions =========================== Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 5.4.295 with commit 264a5cf0c422e65c94447a1ebebfac7c92690670 Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 5.10.239 with commit db5665cbfd766db7d8cd0e5fd6e3c0b412916774 Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 5.15.186 with commit 2ecafe59668d2506a68459a9d169ebe41a147a41 Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 6.1.142 with commit f1c1fdc41fbf7e308ced9c86f3f66345a3f6f478 Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 6.6.94 with commit eb435bc4c74acbb286cec773deac13d117d3ef39 Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 6.12.34 with commit e02e12d6a7ab76c83849a4122785650dc7edef65 Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 6.15.3 with commit 288c39286f759314ee8fb3a80a858179b4f306da Issue introduced in 3.8 with commit 6732ae5cb47c4f9a72727585956f2a5e069d1637 and fixed in 6.16-rc1 with commit 762ef7d1e6eefad9896560bfcb9bcf7f1b6df9c1 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-38286 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/pinctrl/pinctrl-at91.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/264a5cf0c422e65c94447a1ebebfac7c92690670 https://git.kernel.org/stable/c/db5665cbfd766db7d8cd0e5fd6e3c0b412916774 https://git.kernel.org/stable/c/2ecafe59668d2506a68459a9d169ebe41a147a41 https://git.kernel.org/stable/c/f1c1fdc41fbf7e308ced9c86f3f66345a3f6f478 https://git.kernel.org/stable/c/eb435bc4c74acbb286cec773deac13d117d3ef39 https://git.kernel.org/stable/c/e02e12d6a7ab76c83849a4122785650dc7edef65 https://git.kernel.org/stable/c/288c39286f759314ee8fb3a80a858179b4f306da https://git.kernel.org/stable/c/762ef7d1e6eefad9896560bfcb9bcf7f1b6df9c1
Powered by blists - more mailing lists