[Bug 2170572] Re: linux-image-7.0.0-38-generic randomly freezes Lenovo Legion 5

This bug is awaiting verification that the linux/7.3.0-11.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-stonking-linux' to 'verification-done-stonking- linux'. If the problem still exists, change the tag 'verification- needed-stonking-linux' to 'verification-failed-stonking-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-stonking-linux-v2 verification-needed-stonking-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170572 Title: linux-image-7.0.0-38-generic randomly freezes Lenovo Legion 5 Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Status in linux source package in Stonking: Fix Committed Bug description: == SRU Justification == -- Impact An apparmor change in v7.2 caused a NULL pointer validation in some cases. At least one of those happens in a critical section leaving a held lock behind. Which in the end causes the kernel to hang. -- Fix A fix to this was recently released upstream. It would at some point get pulled via stable updates but given the severity of the bug should be given priority. commit 4de32fd05ce9 Author: Maxime Bélair <maxime.belair@canonical.com> Date: Mon Aug 24 17:58:02 2026 +0200 apparmor: fix NULL ctx->peer derefs in unix socket ctx updates -- Test case This seems to require certain HW/setup to happen. And even then might need several restarts. -- Regression potential Anywhere within the area of apparmor controlled socket access. --- original description --- An unattended upgrade from the 7.0.0-31-generic kernel to the 7.0.0-38-generic kernel started causing random freezes on my Lenovo Legion 5 15IAX10 laptop, reverting back to 7.0.0-34-generic seems to fix my issues. I was able to switch to a tty and take a photo (attached), it seems like a kernel bug where CPU is stuck on a spin lock waiting for something. ``` $ grep -C 2 -i "linux-image" /var/log/apt/history.log Start-Date: 2026-10-08 09:10:45 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-image-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-headers-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-tools-7.0.0-38:amd64 (7.0.0-38.38, automatic), linux-headers-7.0.0-38:amd64 (7.0.0-38.38, automatic), linux-tools-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-main-modules-zfs-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic) Upgrade: linux-generic-hwe-24.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-image-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-tools-common:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-headers-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-perf:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-headers-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-image-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), bpftool:amd64 (7.7.0+7.0.0-34.34, 7.7.0+7.0.0-38.38), linux-libc-dev:amd64 (7.0.0-34.34, 7.0.0-38.38) End-Date: 2026-10-08 09:11:28 -- Start-Date: 2026-10-08 09:12:00 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-7.0.0-31-generic:amd64 (7.0.0-31.31), linux-modules-7.0.0-31-generic:amd64 (7.0.0-31.31), linux-main-modules-zfs-7.0.0-31-generic:amd64 (7.0.0-31.31+2) End-Date: 2026-10-08 09:12:06 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170572/+subscriptions