| 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: <2025070331-CVE-2025-38135-20aa@gregkh> Date: Thu, 3 Jul 2025 10:35:52 +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-38135: serial: Fix potential null-ptr-deref in mlb_usio_probe() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: serial: Fix potential null-ptr-deref in mlb_usio_probe() devm_ioremap() can return NULL on error. Currently, mlb_usio_probe() does not check for this case, which could result in a NULL pointer dereference. Add NULL check after devm_ioremap() to prevent this issue. The Linux kernel CVE team has assigned CVE-2025-38135 to this issue. Affected and fixed versions =========================== Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 5.4.295 with commit a05ebe384c7ca75476453f3070c67d9cf1d1a89f Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 5.10.239 with commit 81159a6b064142b993f2f39828b77e199c77872a Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 5.15.186 with commit 19fd9f5a69363d33079097d866eb6082d61bf31d Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 6.1.142 with commit 548b0e81b9a0902a8bc8259430ed965663baadfc Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 6.6.94 with commit a6c7c365734cd0fa1c5aa225a6294fdf80cad2ea Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 6.12.34 with commit c23d87b43f7dba5eb12820f6cf21a1cd4f63eb3d Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 6.15.3 with commit e1b144aebe6fb898d96ced8c990d7aa38fda4a7a Issue introduced in 5.2 with commit ba44dc04300441b47618f9933bf36e75a280e5fe and fixed in 6.16-rc1 with commit 86bcae88c9209e334b2f8c252f4cc66beb261886 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-38135 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/tty/serial/milbeaut_usio.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/a05ebe384c7ca75476453f3070c67d9cf1d1a89f https://git.kernel.org/stable/c/81159a6b064142b993f2f39828b77e199c77872a https://git.kernel.org/stable/c/19fd9f5a69363d33079097d866eb6082d61bf31d https://git.kernel.org/stable/c/548b0e81b9a0902a8bc8259430ed965663baadfc https://git.kernel.org/stable/c/a6c7c365734cd0fa1c5aa225a6294fdf80cad2ea https://git.kernel.org/stable/c/c23d87b43f7dba5eb12820f6cf21a1cd4f63eb3d https://git.kernel.org/stable/c/e1b144aebe6fb898d96ced8c990d7aa38fda4a7a https://git.kernel.org/stable/c/86bcae88c9209e334b2f8c252f4cc66beb261886
Powered by blists - more mailing lists