From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154417; b=rNt5h3ccbOTUQki7KWa4FmXUwDrMPQnxf72X2znmnF20yR7niLk3F4u1Ogc4nYOQYdH1 CQh711TYTDdv2cxU++VK96ldWwLfkZtf++Qk34QIeFQkho9w0i7gi66kN+nRvvSTHTHVj B+IgdOtIR/BolL2UBYM3qwTD+7Kw0A9mOnANtdl9NhezM2x0dvh+M8aCzE+WPJCiz/Jmk mCEVzqOFV7oZif/hjidS77idyG1XqvF9B7qkze9iTwANsRcNAcO7TW4GS0Ch8o/u9uZkM GMSpoJoh5saUTOD8sQ/pkoVmo+YCRnAMcadcl95kQitlf54WNirHaD1FOiX+Pt0TWnQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154417; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=3U0TDEquE9Mf81DNPukfwESJ39jybsG9Ivt1C6O7qig=; b=e9PjEmwA+kK1HahYzeli3VZ57szH4sK7DMIIGEW8cwXz+rGcIgUE4lllYCN5UZb16JhX WxVPegVs6rfUihnekpSB1e/L/S5czMsXm5FzI84oC2nXMyHyFoThD67Vd1PWEBomL360K lTeizkDroI7s/3pX/3H8bHZeTYfKGNu1rEPkcTsj107bcrWtr2Zij8KdlB1iiZcbh5LaG S752IVhOR9M6XzX840XdACatvboRksetJKEi2SvcKUgG6PJPfn3M3U9tnCZtWxjLZe4hO 1kgTyLzoEZjd1tnVXKyK4L3RKtJY+y3tQmwdMWTxJKXY1fSODQEA56xXiLyNB+jFW2g== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=u5lN5rcZ; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 81E27606A32C for ; Fri, 20 Nov 2026 06:00:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=u5lN5rcZ Received: by smtp.kernel.org (Postfix) with ESMTPSA id D24DE1F000D0; Fri, 20 Nov 2026 06:00:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154417; bh=3U0TDEquE9Mf81DNPukfwESJ39jybsG9Ivt1C6O7qig=; h=From:To:Cc:Subject:Date:Reply-To; b=u5lN5rcZ2ySYN6OT6tyLj+lAs0YdB1At3JgBBx2c742cJpqsy2FatGgqkdTA/+ydV GobS6hbjG1Ctyi7S5+PRe1DRGcuTubMTWTmCFiNoEBLA0jqvT9tW1DVO7rUpzCc8Bi +IVdKTQEZ3E0rceQdXODKk4O7JoK8svSmav9SxHU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99736: mm/shmem: fix accounting of swapin-error markers Date: Fri, 20 Nov 2026 06:52:02 +0100 Message-ID: <2026112015-CVE-2026-99736-c44f@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2813; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Oc9KyE7gvaqSoDDh/zv3PaCD+56O1MhoJi5xU5CBT/Q=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/708//PLczq9zo6KSs/L/PHbW37K5pXPPm4Pn2gq5n F4lKxVrd8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEZl9gmB/NbGB4bsGHXrZp tVmaSZIzoifFBTMs2JVmo758sc/sJWJeLg/uRu9SNOevBQA= 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: mm/shmem: fix accounting of swapin-error markers A failed swap read replaces the swap entry with a swapin-error marker in the page-cache and subtracts its pages from "alloced" and "swapped"; however, it leaves their block charge in place. Removing the marker during truncate then subtracts from "swapped" again. This can underflow the counters or make swapped reach zero while other pages remain swapped out, causing swapoff to loop without finding them. When installing the marker, subtract only from "swapped" and let shmem_recalc_inode() reduce "alloced" and release the block charge. Make shmem_free_swap() report successful removal separately from the number of swap pages freed, so removing a swapin-error marker does not subtract from "swapped" again. It's a bit confusing, but replacing a swapped out page by a swapin-error marker in shmem_set_folio_swapin_error() behaves as follows: Initially: alloced=1, swapped=1, nrpages=0 Calling shmem_recalc_inode(inode, 0, -1) -> swapped = 0 -> freed = 1 - 0 - 0 = 1 -> alloced -= freed -> alloced=0, swapped=0, block charge released The Linux kernel CVE team has assigned CVE-2026-99736 to this issue. Affected and fixed versions =========================== Issue introduced in 5.19 with commit 6cec2b95dadf77cdc1256fae1c5dfd4a2b467e61 and fixed in 7.3.5 with commit d4bc03eaeef281c460370dfd57e1a671b787edd4 Issue introduced in 5.19 with commit 6cec2b95dadf77cdc1256fae1c5dfd4a2b467e61 and fixed in 7.4-rc2 with commit 66ce68a249f4ac56cd6968aa6d8ded20fb4b7d09 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-99736 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: mm/shmem.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/d4bc03eaeef281c460370dfd57e1a671b787edd4 https://git.kernel.org/stable/c/66ce68a249f4ac56cd6968aa6d8ded20fb4b7d09