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 2D51B367B68 for ; Tue, 9 Jun 2026 12:26:21 +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=1781007983; cv=none; b=kSh1rPfqiWlMkpHDdZeR7l1MgS0lJwjlhFg8/Kua29o4qvqsoWNlLxt9jg6SFORcmmk+mJHkh3Pz5y94XsiCCjjSXTtlJ+z89pfJClmcP2SUyl1a4Pk6YN9uTAnDFzVVnFHBpNXWNpPIcWTY94V6UgWPHowKOWqmpN5XUrWZJFo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781007983; c=relaxed/simple; bh=c/Km338GHH/79bjTVTNqu6mX6dXX06S39E6JrldZZ7g=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ad9M58Ed2gZpQ2ozDeUksfAL93nR6lGnQ+oqeYeKow6c3tQtUTnqHNOwjcF1e4BBI+s4uuUx7nQVif0S69gXGcGhvKJrQXBGzwo/1zcJmn4KPETr/tqPNCYOZ5WHypUBeQpsBAfZXF9zQxdVGJnNh+uqcJYq48Pf3tkHmpolgxI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Xu1e72aw; 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="Xu1e72aw" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 267A61F00893; Tue, 9 Jun 2026 12:26:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1781007981; bh=YmyWQ1X74uafG6jsOX0pTAZ4fCmUleWYbqjNk3HBPhg=; h=From:To:Cc:Subject:Date:Reply-To; b=Xu1e72awmmDGNsDq0vDPlIukOn2koTeVYtfkQgfbR2/gddqkBcfjTZjdgvSCzOPkg ipwaViQxIVfGoikzwMG6V+HfdTyualJZzDA+RyaDmLDJBTyHVTgadqpGvVHK6WbEeM UH5oCyRmZhflHzBfNkKSdYf8//PYRRZW6UQN+IT4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46328: apparmor: fix rlimit for posix cpu timers Date: Tue, 9 Jun 2026 14:25:11 +0200 Message-ID: <2026060910-CVE-2026-46328-dc30@gregkh> X-Mailer: git-send-email 2.54.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=3332; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6lawPwYP0vSDONywssJXhvo6rCB2G2GVoCbjOvuSSno=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkabGotR51FhcMbVEsScounW1wNWHu9yq/zqOX8goS/8 6ZO9pzQEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABOpC2WYX7zt9qlPGzzYnqzJ OeQZ3yb5/slsU4Z5pncn/uF2Yc9aMiv3s+vkpr1fJ/o3AAA= 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: apparmor: fix rlimit for posix cpu timers Posix cpu timers requires an additional step beyond setting the rlimit. Refactor the code so its clear when what code is setting the limit and conditionally update the posix cpu timers when appropriate. The Linux kernel CVE team has assigned CVE-2026-46328 to this issue. Affected and fixed versions =========================== Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 5.10.252 with commit e1cc11550b2f66687a374536c9dfdddcefca0efe Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 5.15.202 with commit 2232d7cd243833ad750cae656d1817fe43744a09 Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 6.1.165 with commit 28aa93fcfb33b6d580c5df4ae8b6d13fb0e6fcd3 Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 6.6.128 with commit 1f736dfe27c857b78f8461cd7c3dd9640be74b37 Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 6.12.75 with commit e43818b16815c0c2bf933ef28316f8e704e5e0ef Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 6.18.14 with commit 9bf1fa150775b0c6b794e4b6a2c0395e13777999 Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 6.19.4 with commit 57d51d41b90eface809b72e0e009b50546492f1f Issue introduced in 4.10 with commit baa73d9e478ff32d62f3f9422822b59dd9a95a21 and fixed in 7.0 with commit 6ca56813f4a589f536adceb42882855d91fb1125 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-46328 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: security/apparmor/resource.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/e1cc11550b2f66687a374536c9dfdddcefca0efe https://git.kernel.org/stable/c/2232d7cd243833ad750cae656d1817fe43744a09 https://git.kernel.org/stable/c/28aa93fcfb33b6d580c5df4ae8b6d13fb0e6fcd3 https://git.kernel.org/stable/c/1f736dfe27c857b78f8461cd7c3dd9640be74b37 https://git.kernel.org/stable/c/e43818b16815c0c2bf933ef28316f8e704e5e0ef https://git.kernel.org/stable/c/9bf1fa150775b0c6b794e4b6a2c0395e13777999 https://git.kernel.org/stable/c/57d51d41b90eface809b72e0e009b50546492f1f https://git.kernel.org/stable/c/6ca56813f4a589f536adceb42882855d91fb1125