From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7BAFF583AA6 for ; Fri, 11 Sep 2026 19:56:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156601; cv=none; b=h4n8uQq0oYUWHGju8MoSkQSC5vFZCefjdgVmRWj6p+tKm3uWl0fdrJ0ILTrpcJAoqLi73ETgo0YHdBkpOKQ8X510VZ9XQX0S7XPunuo2fmxkzoCj74NSGpRcS0QoHY59mIqUtgs8hTJf1huKutMxS11hab35JH0jrhNsRXoeDpc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156601; c=relaxed/simple; bh=ZXCIGj02kp/LotwM0pmTV3fyJCyCQJrqIqGw0wdbDsg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=CV/Qyi05vRyV5YC3WU9mwOrc1110FkK+xODetvarzLSsBvtz/0+EmCmg6e0fOyKFjectfPfMxquijiCuYmHUomvKMwj4Q0POvoc8ogQnaCbFJupSzo+UzIG43AbIjir3/E2EEVtNXWx0mbHduPsCWPlmo9EA0+kvIrv0Z/fKzXM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=cvMYeFkh; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="cvMYeFkh" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C11011F00893; Fri, 11 Sep 2026 19:56:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156595; bh=4JJMnZkF2vS8qT2lH1VBAx61M1ymdg4cD+ar3ves0o0=; h=From:To:Cc:Subject:Date:Reply-To; b=cvMYeFkhrkoFJQMlvfPZjbymwN7cbVEC6vG7qy+e8vYBs+cjhAgfsbqD4fJHn+pY9 Yssrk4Cz37mFJAWLyrwUDuFq6mpz15NWOMQfKBhGEMdB6tqGIjsOFMbipO9gwHdCLQ 13J3FEziB7YVfCqF99b5wE4+i9YOZ5Q3+z2yDD+Q= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89552: params: fix charp corruption on allocation failure Date: Fri, 11 Sep 2026 21:44:01 +0200 Message-ID: <2026091121-CVE-2026-89552-e2ca@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3019; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=1zBUiwd56JHrteFmndXDnOXsMVupNdc7yx2DBk/Vw8o=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIhPPeXmd8rzMJrMk4W/F+4h3Tv7bkq4+iJj9fNL/9 V5lu9U3dcSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBFshjmyujs02iU+umXzS5m 9Pvfzpf8jbfvMsyVVOP/q7TwcKeXZllb6izHtRtNvX8AAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: params: fix charp corruption on allocation failure param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated. The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL. Failing zswap's compressor update before zswap is initialized can later trigger: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:strcmp+0x10/0x30 Call Trace: zswap_setup+0x3b1/0x490 zswap_enabled_param_set+0x5b/0xa0 param_attr_store+0x93/0xe0 module_attr_store+0x1c/0x30 kernfs_fop_write_iter+0x116/0x1f0 Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds. The Linux kernel CVE team has assigned CVE-2026-89552 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.30 with commit e180a6b7759a99a28cbcce3547c4c80822cb6c2a and fixed in 6.12.109 with commit 614f873268c5b172804c9af6639bd17b7e1e2359 Issue introduced in 2.6.30 with commit e180a6b7759a99a28cbcce3547c4c80822cb6c2a and fixed in 6.18.50 with commit 704ecd010d4a9b33160e40b74eb402f6b86a18e0 Issue introduced in 2.6.30 with commit e180a6b7759a99a28cbcce3547c4c80822cb6c2a and fixed in 7.2.4 with commit 0d8e2404925a0607ffec79a53170715a46936896 Issue introduced in 2.6.30 with commit e180a6b7759a99a28cbcce3547c4c80822cb6c2a and fixed in 7.3-rc1 with commit 3dfaae04243cde460d82dfc2a7dd0bb6664d20ae 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-2026-89552 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: kernel/params.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/614f873268c5b172804c9af6639bd17b7e1e2359 https://git.kernel.org/stable/c/704ecd010d4a9b33160e40b74eb402f6b86a18e0 https://git.kernel.org/stable/c/0d8e2404925a0607ffec79a53170715a46936896 https://git.kernel.org/stable/c/3dfaae04243cde460d82dfc2a7dd0bb6664d20ae