CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent()
driver core: fix potential NULL pointer dereference in devuevent()
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.92.2-1 - Configuration
In the dev_uevent() implementation, use WRITE_ONCE() when setting the driver pointer so the driver instance cannot disappear while it is being accessed; avoid potential NULL pointer dereference.
Linux kernel Use WRITE_ONCE() when setting the driver pointer (dev_uevent() path) = WRITE_ONCE() - Configuration
In dev_uevent(), when fetching the pointer from dev->driver, change to use a valid pointer and take bus' drivers klist lock to prevent the driver from being unbound (dev->driver changing to NULL) during access, avoiding tearing and crashes.
Linux kernel Pointer fetch synchronization in dev_uevent() (bus' drivers klist lock) = Hold bus' drivers klist lock
Event History
Frequently Asked Questions
What is the severity of CVE-2025-37800?
CVE-2025-37800 has been rated as a moderate severity vulnerability due to the potential for a NULL pointer dereference.
How do I fix CVE-2025-37800?
To fix CVE-2025-37800, ensure that your Linux kernel is updated to the latest version that includes the patch for this vulnerability.
What systems are affected by CVE-2025-37800?
CVE-2025-37800 affects the Linux Kernel across various distributions that utilize this kernel version.
Can CVE-2025-37800 lead to a system crash?
Yes, CVE-2025-37800 can potentially result in a system crash due to the NULL pointer dereference issue.
Is CVE-2025-37800 an exploit in the Linux kernel?
CVE-2025-37800 is a vulnerability that can be exploited if not patched, allowing for potential disruption in device handling.