CVE-2024-36885 in Linux
Zusammenfassung
von VulDB • 29.05.2026
Based on the stack trace provided, here is an analysis of the issue:
### **Summary** The system is crashing (likely a kernel panic or oops) while loading the **Nouveau** open-source NVIDIA GPU driver. The crash occurs during the initialization of the DRM (Direct Rendering Manager) device, specifically when trying to create a new NVKM udevice.
### **Key Stack Trace Analysis** 1. **Crash Location**: ``` __pfx_nvkm_udevice_new+0x10/0x10 [nouveau]
``` This indicates the crash happened inside `nvkm_udevice_new`, a function in the NVKM (NVIDIA Kernel Module) subsystem, which is the core of the Nouveau driver. The `+0x10/0x10` suggests it’s a very short function or a wrapper, possibly failing early in object construction.
2. **Call Chain**: - `nouveau_cli_init` → `nouveau_drm_device_init` → `nouveau_drm_probe` - This is the standard initialization path for the Nouveau DRM driver when a PCI device is probed. - The driver is trying to set up the user-space interface (`nvif_object_ctor` → `nvif_device_ctor` → `nvkm_udevice_new`).
3. **Context**: - The crash happens during `init_module_from_file` → `__x64_sys_finit_module`, meaning the crash occurred while **loading the kernel module** (likely via `modprobe nouveau` or during boot if the module is built-in and triggered by PCI probe). - The `RIP` (Instruction Pointer) is in user-space (`0x7feeb5cc20cd`), which is unusual for a kernel oops. This often happens if: - The kernel oops was caught and reported via a signal to a user-space process (e.g., `systemd`, `udev`, or a display manager). - Or, the trace is from a user-space crash that triggered a kernel dump (less likely given the kernel stack). - **Most likely**: The kernel crashed, and the crash dump was captured while a user-space process was in the middle of a syscall (like `finit_module`).
### **Common Causes** 1. **Incompatible Kernel/Nouveau Version**: - The Nouveau driver may not support your specific NVIDIA GPU architecture (e.g., newer GPUs like Turing/Ampere/Hopper may have limited or broken support in older kernels). - Check your GPU model (`lspci -nn | grep -i vga`) and compare it with [Nouveau GPU Support](https://nouveau.freedesktop.org/FeatureMatrix.html).
2. **Kernel Bug**: - A regression in the `nvkm_udevice_new` function in your specific kernel version. - Check if this is a known bug in your kernel version (e.g., search for `nvkm_udevice_new nouveau crash` on kernel.org or your distro’s bug tracker).
3. **Hardware Issue**: - Rare, but possible if the GPU is faulty or has PCIe communication issues.
4. **Conflicting Drivers**: - Ensure the proprietary `nvidia` driver is not partially loaded or conflicting with Nouveau.
### **Troubleshooting Steps**
#### 1. **Identify Your GPU and Kernel Version** ```bash lspci -nn | grep -i vga uname -r ```
#### 2. **Check dmesg for More Details** ```bash dmesg | tail -50 ``` Look for errors before the crash, such as: - `nouveau: [GPU ERROR]`
- `NVRM: Xid ...` - `BUG: unable to handle kernel NULL pointer dereference`
#### 3. **Try Blacklisting Nouveau** If you don’t need open-source drivers, blacklist Nouveau and use the proprietary NVIDIA driver: ```bash echo "blacklist nouveau" | sudo tee /etc/modprobe.d/blacklist-nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf sudo update-initramfs -u # Debian/Ubuntu sudo dracut --force # RHEL/Fedora ``` Then reboot and install the proprietary NVIDIA driver.
#### 4. **Update Kernel** If you’re on an older kernel, try updating to a newer version where Nouveau support may have improved.
#### 5. **Test with `nomodeset`** Add `nomodeset` to your
If you want to get best quality of vulnerability data, you may have to visit VulDB.