CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent()
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.
Security readout for executives and security teams
Plain-English summary
A race in the Linux kernel device-driver subsystem can dereference an invalid driver pointer when one process reads a device’s uevent attribute while another unbinds that device. The documented result is a kernel crash, creating local denial-of-service risk. The CVSS record also indicates possible confidentiality impact, but the supplied description does not explain that impact.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared or multi-tenant Linux systems. It is less urgent than a remotely exploitable vulnerability, but successful triggering may crash the host. Follow distribution guidance promptly; emergency action is not supported by the supplied exploitation evidence.
Technical view
Concurrent uevent reads and driver unbinding can change dev->driver from valid to NULL during access. The kernel fix fetches the pointer with READ_ONCE(), protects driver lifetime using the bus drivers klist lock, and applies WRITE_ONCE() when assigning the pointer to prevent tearing.
Likely exposure
Exposure applies to affected Linux kernel builds where a low-privileged local user can reach the relevant device attribute while driver unbinding occurs. The record lists affected versions from 2.6.22 through several 2025 branches, but its version data is insufficient to determine precise distribution package boundaries.
Exploitation context
The supplied record does not report known active exploitation, and CVE-2025-37800 is not identified as KEV. Exploitation requires local access and a specific concurrency condition. A kernel crash is documented; the source bundle provides no exploit evidence or demonstrated information-disclosure mechanism.
Researcher notes
The CVSS 3.1 vector is 7.1: local, low complexity, low privileges, no interaction, with high confidentiality and availability impacts. Only the crash condition is described. Exact affected and fixed package ranges remain distribution-specific, and the bundle’s duplicated commit identifier and unusual version entry “0” reduce version-boundary confidence.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix or distribution backport.
Check Linux distribution advisories for exact fixed package versions before deployment.
Prioritize multi-user systems where untrusted local users can access relevant device attributes.
Use normal change controls and reboot into the updated kernel when required.
Validation and detection
Record each system’s running kernel version and distribution package release.
Confirm the vendor package includes one of the referenced fixes or an equivalent backport.
Verify systems booted into the updated kernel after installation.
Review local-user exposure and permissions around device management interfaces.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-37800 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.