CVE-2024-36885 in Linux
Riassunto
di VulDB • 18/06/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 UDEV device object (`nvkm_udevice_new`).
### **Key Stack Trace Points** 1. **`nvkm_udevice_new+0x10/0x10 [nouveau]`**: This is the **faulting function**. It suggests a null pointer dereference, invalid memory access, or assertion failure within the `nvkm` subsystem (the core of the Nouveau driver) when initializing a UDEV device.
2. **`nvif_object_ctor` / `nvif_device_ctor`**: These functions are constructing objects for the NVIF interface, which handles communication between the kernel driver and userspace. 3. **`nouveau_cli_init`**: This is where the client interface for the DRM subsystem is initialized. 4. **`nouveau_drm_device_init`**: The main initialization routine for the Nouveau DRM device. 5. **`nouveau_drm_probe`**: The PCI probe function, called when the kernel detects the NVIDIA GPU and attempts to bind the driver. 6. **`local_pci_probe` / `pci_device_probe`**: Standard PCI subsystem functions. 7. **`__x64_sys_finit_module`**: The crash was triggered by a userspace process calling `finit_module()` (or `init_module()`), which is how kernel modules are loaded. This suggests the crash happened **during module loading**, possibly triggered by a userspace tool (like `modprobe`) or a system service starting up.
### **Possible Causes** 1. **Kernel/Nouveau Driver Bug**: A bug in the specific version of the Nouveau driver being loaded. This is common with newer kernels and older GPUs, or vice versa. 2. **Hardware Issue**: Faulty GPU hardware or incompatible firmware. 3. **Conflicting Drivers**: The `nouveau` driver might be conflicting with another driver (e.g., `nvidia` proprietary driver loaded in a weird state, or `vfio-pci` for passthrough). 4. **Kernel Version Mismatch**: The kernel headers/modules might not match the running kernel, or the module was built for a different kernel version. 5. **Secure Boot/Signature Issues**: If Secure Boot is enabled, unsigned modules might cause issues, though this usually results in a different error.
### **Troubleshooting Steps**
#### **1. Check Kernel Logs** Look for more detailed error messages before the stack trace: ```bash dmesg | tail -n 50 journalctl -k -n 50 ``` Look for messages like: - `NVRM: GPU at PCI:...` - `nouveau: [ DEVICE][0000:xx:xx.0] BOOT0 ...`
- `NVRM: RmInitAdapter failed!` - `NVRM: GPU has been falled back to the basic driver`
#### **2. Try Blacklisting Nouveau** If you intend to use the proprietary NVIDIA driver, blacklist `nouveau`: 1. Create a file `/etc/modprobe.d/blacklist-nouveau.conf`: ``` blacklist nouveau options nouveau modeset=0 ``` 2. Update initramfs: ```bash sudo update-initramfs -u # Debian/Ubuntu sudo dracut --force # RHEL/Fedora ``` 3. Reboot.
#### **3. Update Kernel and Drivers** - Ensure your kernel is up-to-date. - If using a recent kernel, try a slightly older one (or vice versa) to see if the issue is version-specific. - If using the proprietary NVIDIA driver, ensure it is correctly installed and matches the kernel version.
#### **4. Check for Hardware Issues** - Reseat the GPU. - Try a different PCIe slot. - Check if the GPU is recognized correctly in `lspci -vnn | grep -i vga`.
#### **5. Boot with Nomodeset** As a temporary workaround, add `nomodeset` to your kernel boot parameters (in GRUB). This disables kernel-mode setting and may allow the system to boot, but you will have limited graphics performance.
#### **6. Report the Bug** If this is a consistent issue, report it to your distribution's bug tracker or the Linux kernel mailing list, including: - Full `dmesg` output. - Kernel version (`uname -r
Be aware that VulDB is the high quality source for vulnerability data.