PVE 7.4-16 / 5.15.108-1-pve BUG: kernel NULL pointer dereference


New Member
Aug 12, 2023
Hi all!

I'm facing random kernel panic in PVE7 since updated to 5.15.108-1.
Last weekend I just upgraded the entire server, rebooted and around 15 hours later I found this kernel panic.

Tried several options from other posts, memtest pass without errors, looked at CPU temp, rebooted several times... it happens randomly.
However, if I revert to kernel 5.15.107-2-pve all start working nice again, without any other changes needed.

So, I guess come regression have happened in this kernel version, like in this older issue: https://forum.proxmox.com/threads/p...error_code-0x0000-no-web-access-no-ssh.96598/

So far, see attached journal with log.
Can anybody take a look at this issue?

Thank you!


  • Syslog.log
    169.1 KB · Views: 4

Just in case (booted from working kernel):

proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-16 (running version: 7.4-16/0f39f621)
pve-kernel-5.15: 7.4-4
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-5
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1
Last edited:
Regrettably I faced a recent loss from what I can only describe as an upgrade related bug from the most recent 'pve-kernel-5.15.108-1-pve' release.

After the update, the OS booted, however much of the underlying components that allowed PVE to function were wiped out.

I did have a zip archive of a backup (tar) from this repo ( https://github.com/DerDanilo/proxmox-stuff ) running on the system, however it didn't remediate the breakage to the hypervisor functions (while Debian itself seemed to be ok).

I simply reinstalled PVE from scratch and reloaded all guest systems from the prior evening backup.

Now, I'm not pointing any fingers, and I've been using PVE for many years, and will continue to use it as I still see it being stable enough 99% of the time, but I just wanted to share my recent experience per this latest release.

Additionally when running the apt update (where I typically launch the process via Webmin), the 'pve-kernel-helper' package did come back with unmet dependencies, and I following this warning, I did pick and choose packages around the lack of this package installing (resulting in a warning), and chose to dis-include this package which could have been the fatal mistake in my situation.
Last edited:


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!