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 Kernel
Packages, which is subscribed to linux-hwe-6.5 in 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)
Status in linux-hwe-6.5 package in Ubuntu:
Confirmed
Bug description:
Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few
minutes after the boot.
I can't find anything in the journal for the previous boot it just ends
without any error. Remote syslog server does not receive any error log from
this host. I've tried running journalctl on the local console and wait for the
hang got nothing.
On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the
screen and the rest is what was on the console before the hang:
ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48
Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
so it is definitely the new kernel.
I don't have enough time to generate report with ubuntu-bug on the new
kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
