From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46328: apparmor: fix rlimit for posix cpu timers
Date: Tue, 9 Jun 2026 14:25:11 +0200 [thread overview]
Message-ID: <2026060910-CVE-2026-46328-dc30@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-06-09 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026060910-CVE-2026-46328-dc30@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.