| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37883: s390/sclp: Add check for get_zeroed_page() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| s390/sclp: Add check for get_zeroed_page() |
| |
| Add check for the return value of get_zeroed_page() in |
| sclp_console_init() to prevent null pointer dereference. |
| Furthermore, to solve the memory leak caused by the loop |
| allocation, add a free helper to do the free job. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37883 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.15.181 with commit e1e00dc45648125ef7cb87ebc3b581ac224e7b39 |
| Fixed in 6.1.136 with commit 397254706eba9d8f99fd237feede7ab3169a7f9a |
| Fixed in 6.6.89 with commit 28e5a867aa542e369e211c2baba7044228809a99 |
| Fixed in 6.12.26 with commit 3b3aa72636a6205933609ec274a8747720c1ee3f |
| Fixed in 6.14.5 with commit f69f8a93aacf6e99af7b1cc992d8ca2cc07b96fb |
| Fixed in 6.15 with commit 3db42c75a921854a99db0a2775814fef97415bac |
| |
| 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-37883 |
| 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/s390/char/sclp_con.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/e1e00dc45648125ef7cb87ebc3b581ac224e7b39 |
| https://git.kernel.org/stable/c/397254706eba9d8f99fd237feede7ab3169a7f9a |
| https://git.kernel.org/stable/c/28e5a867aa542e369e211c2baba7044228809a99 |
| https://git.kernel.org/stable/c/3b3aa72636a6205933609ec274a8747720c1ee3f |
| https://git.kernel.org/stable/c/f69f8a93aacf6e99af7b1cc992d8ca2cc07b96fb |
| https://git.kernel.org/stable/c/3db42c75a921854a99db0a2775814fef97415bac |
