# CVE-2025-39837: platform/x86: asus-wmi: Fix racy registrations

> A race condition in the ASUS WMI driver can cause memory corruption and system crashes on ASUS machines.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 19 Sep 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-39837, DEBIAN-CVE-2025-39837, GHSA-g3gw-5g8v-fphj, UBUNTU-CVE-2025-39837

## What is CVE-2025-39837?

CVE-2025-39837 is a high-severity vulnerability in Linux kernel, published on 19 Sep 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:

platform/x86: asus-wmi: Fix racy registrations

asus_wmi_register_driver() may be called from multiple drivers
concurrently, which can lead to the racy list operations, eventually
corrupting the memory and hitting Oops on some ASUS machines.
Also, the error handling is missing, and it forgot to unregister ACPI
lps0 dev ops in the error case.

This patch covers those issues by introducing a simple mutex at
acpi_wmi_register_driver() & *_unregister_driver, and adding the
proper call of asus_s2idle_check_unregister() in the error path.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-39837 being exploited?

There is no known exploitation of CVE-2025-39837 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-39837 and fix it if it is affected.

What it is: CVE-2025-39837 is a high-severity vulnerability in Linux kernel, published on 19 Sep 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-39837 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-39837/ (Markdown: https://insights.sbomify.com/CVE-2025-39837/index.md)
```

## Sources

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

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