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=1795100507; b=hBH0cZ+PCMm4L83wfqrVBtmssIMKnVne1rvXFQIE+y10Q1JsGKg4YfVizs6l0m6nmuyp 65YHNhLKebd1tog1HWG3Wg4PmqqQlsXj5YWDlj90Xzh1RI7+pYD+o0eJni+pwJRiYCe2T 6FY0yvXlCqMFChBCh5LsxGOVfg4FTBnGTgu8Pjc0PpGdxHpyTlsECanX/Up0FRe8ZZI/4 csqEfFVnzK2mAxUk7HxdTB2K4NgYvDVKx0g2wLHq/yJMV8LiW4NnX2WwODI+SeG9DKmpx Bsn0XimRN2ewOgzSJfKsKTtf9E2nEs1nLnDjWhGV0//rTWHwxrSfBb4nunyhxmVWAQg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795100507; 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=ePtSHKminKBozcxK7eYHkzSnOzeChPeJ4dceQ2RifeQ=; b=uXDYCvXf1cDD7vu9zu5IA8PNKKCI3ff6dSLNKLZBlvgrJ8FpIfNWYBjxRSte3TFNe0Nk jf3Ful223sXo9Bi77gfuhlBF76m7Yb9P/K8MHmDgNNKe4Vd+7YBiekhD63yxM0NPsRC1p Ku17Ws3SI49eMSgzhjC57WZ7PgFED4wzP70tBsawP70kCsiFk18uJ9Gk9fodpMTU5p7DK F86GOuUwo7/kIJX2Bu+jKicUgr0DBe1thUc++y0qeP76f916pISd8PY4ouaiwonnsf4iR YSkyZTMJivnz/+z71XovN96vBz2M4dEsWIW6DvvNHLy1coukb7SXOaiMHRwe41qhTzQ== 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=0CPjzlOe; 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 7F486606A320 for ; Thu, 19 Nov 2026 15:01:47 +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=0CPjzlOe Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4AF041F000C5; Thu, 19 Nov 2026 15:01:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795100507; bh=ePtSHKminKBozcxK7eYHkzSnOzeChPeJ4dceQ2RifeQ=; h=From:To:Cc:Subject:Date:Reply-To; b=0CPjzlOeJoMUNkuTCZIY7hrJQNoYqNar/q8Y3cpPIpOzM/93JYb5lEgczeK3sBdeH Oz2bk3QLcm4Em9AnvZRgQchcm/XGk/MDXH/e2WhtoWcQwZB4ttMJHNdsO56EDxG8PO v8TwX/tAEa961j8uu0q99Nin6XFKLfkb6RoGtFiI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99520: pps: generators: fix use-after-free when closing a removed device Date: Thu, 19 Nov 2026 15:26:58 +0100 Message-ID: <2026111920-CVE-2026-99520-be01@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=3227; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=F3mIDlYzccVkhe2AGospeWBlF2QXOPlJaSAC6MhcXnE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2aactTWcOHWuy7HaRzpXmiQNujh6eTznXmNKfmufv GHCbU3ejlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiIawjDfIfSs+66Gx9dKthR ZnfZl91Z/tWJLob5ldcj/3PzX59l45YWu+pIWK3cr34WAA== 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: pps: generators: fix use-after-free when closing a removed device The cdev of a PPS generator is embedded in struct pps_gen_device, but nothing ties the lifetime of that structure to the cdev: pps_gen is freed by the release function of its device, and an open file holds a device reference only until pps_gen_cdev_release() drops it. When the generator is unregistered while /dev/pps-genN is open, that put_device() drops the last reference and frees pps_gen, and __fput() then calls cdev_put() on the freed cdev: BUG: KASAN: slab-use-after-free in cdev_put+0x53/0x60 Read of size 8 at addr ffff88801383e138 by task ppsgen64/149 Call Trace: cdev_put+0x53/0x60 __fput+0x745/0xad0 fput_close_sync+0xd9/0x1b0 __x64_sys_close+0x86/0xf0 ... Freed by task 149: kfree+0x25a/0x6d0 device_release+0xca/0x3c0 kobject_put+0x169/0x320 pps_gen_cdev_release+0x51/0x80 __fput+0x36a/0xad0 pps.c had the same bug, fixed in commit c79a39dc8d06 ("pps: Fix a use-after-free"). Fix it the usual way: embed the struct device in pps_gen_device and register both with cdev_device_add(). This makes the device the parent of the cdev, so the cdev holds a device reference until the last file is closed. The Linux kernel CVE team has assigned CVE-2026-99520 to this issue. Affected and fixed versions =========================== Issue introduced in 6.14 with commit 86b525bed2758878e788c9fb6b8fb281fd61bdb0 and fixed in 6.18.61 with commit 63dc56500a91591ad9b42e09ca4646b0a4d03406 Issue introduced in 6.14 with commit 86b525bed2758878e788c9fb6b8fb281fd61bdb0 and fixed in 7.3.2 with commit 3c94478114384d97795029160ceb539ade38cc43 Issue introduced in 6.14 with commit 86b525bed2758878e788c9fb6b8fb281fd61bdb0 and fixed in 7.4-rc1 with commit d19552611cb2eb6329826871565e5309bec2f288 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-99520 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/pps/generators/pps_gen.c include/linux/pps_gen_kernel.h 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/63dc56500a91591ad9b42e09ca4646b0a4d03406 https://git.kernel.org/stable/c/3c94478114384d97795029160ceb539ade38cc43 https://git.kernel.org/stable/c/d19552611cb2eb6329826871565e5309bec2f288