All reports
Medium

kernel: driver core: fix potential NULL pointer dereference in dev_uevent()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-37800

Probability of exploitation in the next 30 days: 0.21%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential NULL pointer dereference in dev_uevent() If userspace reads "uevent" device attribute at the same time as another threads unbinds the device from its driver, change to dev->driver from a valid pointer to NULL may result in crash. Fix this by using READ_ONCE() when fetching the pointer, and take bus' drivers klist lock to make sure driver instance will not disappear while we access it. Use WRITE_ONCE() when setting the driver pointer to ensure there is no tearing.

A flaw was found in the Linux kernel's driver core subsystem. A race condition can occur when a local user reads a device's uevent attribute at the same time another thread unbinds the device from its driver. This concurrent operation can result in a null pointer dereference in the dev_uevent() function, causing a system crash and resulting in a Denial of Service (DoS).