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=1795099522; b=SxcNegk/IMaB9NrHOGp0fEDN8onpkhuFKiaEXJX4pnEsMCe9umvoyNZeCDpK3cNiANY2 QZ7h5DygeZZ2oZ5ToyoucPcp56eLeaihex7/haFi81Xk7z678vUP5Q1LxXw6kXv3Bsky/ JhWexMENdGk6Hrx6jAZcvIqIIKBdZyTv0UAHf17UM02JKJmoXGnrecRD3o3ieg5XHRH+V zid7LVOJhd7klKPBUAenrhp69sHRO2Ky22YUQ93fWTF9MeoJO5s45QzvvB/p7WsA1zaV/ gVzWYBQDuRQLtzpEOiDjaP9aJb016IwXroowJyTzzafXpLBPzWyXC0bWEFBTDi7654g== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099522; 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=X/LvvtdcMjNnyYtOy/8vRBFsu19Enk6OLRPhXkrk+yU=; b=Dv2jJI2sOnlT8OKh0Ig1PuR+HbebnkLq8YhEz50y1ihnToKqQUX7aDNpZj83jAsS/CML 0+ecIkpv8qn3YT2X1vtx5Jzogjr5eYfp5k/cbgi2FsOjKMMkbGSZurM9z7k435qgPuI/v 0XO5mDrETjHOnjoCxQn8Q2moFZfHW3xYIgryG1NivmYK3gs+UmdBxwbT51dlstySWEYbm ePR5CntDx8wm4OIliTEUMbomvjLiA6cDW+VUnVDPWJbyrP0zxVJovCgkjLgEZVLkRuHfP 0fL+4+PvAh5AUnGeg80GLJG1aMNjbnZ8whVqUiJqKZOi5heDVUPItyIYJlGDl6QsZDA== 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=y79EZDeN; 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 49142606A326 for ; Thu, 19 Nov 2026 14:45:22 +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=y79EZDeN Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0411D1F000C5; Thu, 19 Nov 2026 14:45:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099521; bh=X/LvvtdcMjNnyYtOy/8vRBFsu19Enk6OLRPhXkrk+yU=; h=From:To:Cc:Subject:Date:Reply-To; b=y79EZDeNzXbPB+A54MYEBfrcNiwKTqKpXsN3ctKionGEyVr6uT8DL8yuYYBWalhQN EFSKZzHitloIWl1Mr8hZwmFPxXfXOqfSkZTSKBCKGaKJ0OLM9pPl8SLkfpA3bqaGPF gi/cxhRDy+01tZsz0ci4otvGHcJSeeDWnmNFJvRg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99418: ovl: do not copy up an xattr value that was never read Date: Thu, 19 Nov 2026 15:25:16 +0100 Message-ID: <2026111900-CVE-2026-99418-131d@gregkh> X-Mailer: git-send-email 2.56.0 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=3201; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=HFJT+y2eNX1AVGNt6cC4igE+diWhGcE5OMz7fzbcq3k=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2RqUfXJFLjzWns+6vXl7eI3DwuaSD38K/u27xbnCe P3N3H63jlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIdT3DfO+2/sTK3/etbj5k 2uZdeLbqzcfo3Qzzo3ZaaBr9sHxnwha15R+X99O3J8I3AwA= 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: ovl: do not copy up an xattr value that was never read Copy-up stores uninitialized kernel memory in an xattr of the upper file, where the user can read it. ovl_copy_xattr() may only pass bytes to ovl_do_setxattr() that ovl_do_getxattr() has read. When the read fails with -ERANGE the function asks for the size again, and if the new size fits the buffer it stores the buffer although nothing was read into it. The buffer comes from kvmalloc(), or it still holds the value of the previous xattr. A FUSE lower layer that answers every sized GETXATTR with -ERANGE made copy-up store 4096 bytes that the server never sent, with a kernel pointer in them, as an xattr of the upper file. Fix this by failing the copy-up with -EIO when the size that follows -ERANGE fits the buffer. The Linux kernel CVE team has assigned CVE-2026-99418 to this issue. Affected and fixed versions =========================== Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 6.12.117 with commit 3b1f5a4652539014f0162944f1a5f71ee520188a Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 6.18.61 with commit 628260a7204314ab5f1cd93bddb1721cc0226b38 Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 7.3.2 with commit e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7 Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 7.4-rc1 with commit 755b5c5c9277be251a51623d6065abab948c61bc Issue introduced in 3.18.27 with commit f641fdbd8ca737df49e96d9d58206fb0a9d82512 Issue introduced in 4.1.18 with commit 3c0a63d74b4a12a0a98cd85b195031d8d4b109a6 Issue introduced in 4.4.3 with commit fa932190a5f332e1936ab0223c7c5d79b5596a9c 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-99418 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: fs/overlayfs/copy_up.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/3b1f5a4652539014f0162944f1a5f71ee520188a https://git.kernel.org/stable/c/628260a7204314ab5f1cd93bddb1721cc0226b38 https://git.kernel.org/stable/c/e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7 https://git.kernel.org/stable/c/755b5c5c9277be251a51623d6065abab948c61bc