Hello,
with v6.12 we encountered a kernel BUG (panic on our systems) that is caused by a NULL pointer dereference inside the apparmor's profile_transition code. I've contacted John Johansen as the maintainer for the apparmor system, and he pointed me to 17d0d04f3c99 as a fix for that issue. That commit has now landed in v6.13, would it be possible to backport this to v6.12? Commit is
17d0d04f3c99 apparmor: allocate xmatch for nullpdb inside aa_alloc_null
Thanks,
Paul
On Tue, Jan 21, 2025 at 11:55:21AM +0100, Paul Kramme wrote:
Hello,
with v6.12 we encountered a kernel BUG (panic on our systems) that is caused by a NULL pointer dereference inside the apparmor's profile_transition code. I've contacted John Johansen as the maintainer for the apparmor system, and he pointed me to 17d0d04f3c99 as a fix for that issue. That commit has now landed in v6.13, would it be possible to backport this to v6.12? Commit is
17d0d04f3c99 apparmor: allocate xmatch for nullpdb inside aa_alloc_null
Now queued up, thanks.
greg k-h
linux-stable-mirror@lists.linaro.org