I just started SDDM then the driver crashed. GPU: GTX 1060 Driver: 580.142 This bug is reproducible at 100%. Rolling back to the 580.126.18 driver is the only way to get my PC usable. [ 2164.202115] BUG: kernel NULL pointer dereference, address: 0000000000000028 [ 2164.202122] #PF: supervisor re…

Bug ID 5983006 created for same. I will check and revert back.

I could see few traces of driver mismatch, can you clean all traces of older driver 580.126.18 and reinstall the latest driver again? I will wait for your response.

I unloaded the old driver (580.126.18), installed the new driver (580.142) with the package manager then loaded the new driver. This is why you see traces of the old driver, but even in that case, unloading a driver shouldn’t corrupt the kernel state. I tested again starting the PC only with the ne…

I reverted nvidia-drm-fb.c by applying the following patch and the driver didn’t crash anymore. diff --git a/nvidia-drm/nvidia-drm-fb.c b/nvidia-drm/nvidia-drm-fb.c index 05506435..d6f38ee8 100644 --- a/nvidia-drm/nvidia-drm-fb.c +++ b/nvidia-drm/nvidia-drm-fb.c @@ -141,7 +141,6 @@ static int nv_dr…

Not looked closely at the code but, if I were to take a guess, when non_scanout_mem_backedis true, the function returns 0 rather than -EINVAL (without goto fail) and a user of this function may be expecting that pSurface is not NULL if it returned 0.

Thanks, we have successfully reproduced this issue locally here at NVIDIA Labs, our engineers are taking look.

This revert wasn’t applied in nvidia-580.159.03, is that correct?

Both 595.58.03 and 595.71.05 are also affected by the issue.

Confirming this bug on a different GPU and a later driver version, with what looks like a specific reproduction trigger. System: GPU: NVIDIA GeForce GTX 1050 Ti Mobile (Pascal, GP107M) Driver: 580.159.03 (latest 580 release at time of writing) Distro: Kubuntu 26.04 LTS Kernel: 7.0.0-15-generic DE…

Kernel NULL pointer dereference when using the 580.142 driver

Graphics / Linux Linux

ionen April 30, 2026, 2:09pm 9

Haven’t tried myself but one of our user has confirmed that this issue still happens, and the file had no changes since 580.142. So, not fixed yet.

Topic		Replies	Views
Kernel NULL pointer dereference, address: 000000000000022c Linux	0	451	June 15, 2023
Kernel Error Linux kernel	1	2042	November 9, 2021
null pointer dereference error in driver. Linux	1	885	February 1, 2018
Unable to handle kernel NULL pointer dereference at 0000000000000f28 Linux	1	1474	March 11, 2019
340.58 and vanilla kernel: BUG: unable to handle kernel NULL pointer dereference Linux	6	4044	April 7, 2015
Kernel NULL pointer dereference, address: 0000000000000097 - 550.x version Linux	0	474	May 5, 2024
Kernel panic due to a NULL pointer dereference at 0000000000002b20 Linux	5	2785	March 10, 2023
NULL pointer dereference under wayland shortly after nvidia-powerd start Linux	2	668	May 8, 2022
Bug report: 455.23.04 - Kernel Panic due to NULL pointer dereference Linux	235	44697	July 19, 2023
Nvidia 525 crash kernel NULL pointer dereference Linux	2	724	December 6, 2022

Kernel NULL pointer dereference when using the 580.142 driver

Related topics