Answer in brief
CVE-2025-39837 records a Unknown severity vulnerability in platform/x86: asus-wmi: Fix racy registrations. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=feea7bd6b02d43a794e3f065650d89cf8d8e8e59 <e7a70326fb26b905cfc8fe2366113aa4394733ef || >=feea7bd6b02d43a794e3f065650d89cf8d8e8e59 <5549202b9c02c2ecbc8634768a3da8d9e82d548d | e7a70326fb26b905cfc8fe2366113aa4394733ef, 5549202b9c02c2ecbc8634768a3da8d9e82d548d |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39837 records a Unknown severity vulnerability in platform/x86: asus-wmi: Fix racy registrations. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=feea7bd6b02d43a794e3f065650d89cf8d8e8e59 <e7a70326fb26b905cfc8fe2366113aa4394733ef || >=feea7bd6b02d43a794e3f065650d89cf8d8e8e59 <5549202b9c02c2ecbc8634768a3da8d9e82d548d | e7a70326fb26b905cfc8fe2366113aa4394733ef, 5549202b9c02c2ecbc8634768a3da8d9e82d548d |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.