Here on 6.8.0-40-generic
My guess is that structure representing mount options changed in
Apparmor resulting in a mismatch between the user/kernel side.
I've an AppImage, generated with genprof but after a couple of `aa-
logprof` runs, it stopped working (while still in complain mode!)...
because this line triggered a OOPS very similar (if not identical) to
the above (attached)
> apparmor="ALLOWED" operation="mount" class="mount" info="failed mntpnt
match" error=-13 profile="/usr/local/bin/foobar"
name="/tmp/.mount_foobarfDWxdu/" pid=147850 comm="foobar"
fstype="fuse.foobar" srcname="foobar" flags="ro, nosuid, nodev"
I couldn't isolate the actual profile change triggering this but it's likely
related to fuse/custom fstype/mount options within one of the profiles. Some of
the rules (related to fusermount3, which may deserve a check):
```
capability dac_read_search,
/dev/fuse rw,
/etc/fuse.conf r,
/proc/*/mounts r,
/usr/bin/fusermount3 mr,
owner /etc/nsswitch.conf r,
owner /etc/passwd r,
```
** Attachment added: "oops on an AppImage"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+attachment/5814102/+files/oops.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
Kernel Oops - kernel NULL pointer dereference
(apparmor_bprm_creds_for_exec, profile_transition) with linux-
image-6.5.0-18-generic (linux-image-generic-hwe-22.04)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
