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: <2025070418-CVE-2025-38201-9575@gregkh> Date: Fri, 4 Jul 2025 15:37:30 +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-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX Otherwise, it is possible to hit WARN_ON_ONCE in __kvmalloc_node_noprof() when resizing hashtable because __GFP_NOWARN is unset. Similar to: b541ba7d1f5a ("netfilter: conntrack: clamp maximum hashtable size to INT_MAX") The Linux kernel CVE team has assigned CVE-2025-38201 to this issue. Affected and fixed versions =========================== Fixed in 6.12.35 with commit 0ab3de047808f375a36cd345225572eb3366f3c6 Fixed in 6.15.4 with commit d2768016f091f8a5264076b433fd7c3fabb6eb97 Fixed in 6.16-rc1 with commit b85e3367a5716ed3662a4fe266525190d2af76df 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-38201 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: net/netfilter/nft_set_pipapo.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/0ab3de047808f375a36cd345225572eb3366f3c6 https://git.kernel.org/stable/c/d2768016f091f8a5264076b433fd7c3fabb6eb97 https://git.kernel.org/stable/c/b85e3367a5716ed3662a4fe266525190d2af76df
Powered by blists - more mailing lists