# CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent()

> A race condition in the Linux kernel driver core can cause a NULL pointer dereference and system crash when unbinding a device while reading its uevent attribute.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-63788, BELL-CVE-2025-37800, DEBIAN-CVE-2025-37800, GHSA-3g6q-j56q-qw54, ROOT-OS-DEBIAN-11-CVE-2025-37800, ROOT-OS-DEBIAN-12-CVE-2025-37800, ROOT-OS-UBUNTU-2204-CVE-2025-37800, ROOT-OS-UBUNTU-2404-CVE-2025-37800, UBUNTU-CVE-2025-37800

## What is CVE-2025-37800?

CVE-2025-37800 is a high-severity vulnerability in Linux kernel, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-37800?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-37800?

Apply the vendor's patch.

## Is CVE-2025-37800 being exploited?

There is no known exploitation of CVE-2025-37800 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37800 and fix it if it is affected.

What it is: CVE-2025-37800 is a high-severity vulnerability in Linux kernel, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37800 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-37800/ (Markdown: https://insights.sbomify.com/CVE-2025-37800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-37800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-37800
- OSV: https://osv.dev/vulnerability/CVE-2025-37800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-37800/
Summaries are generated and may contain mistakes; the official description above is the record.