Linux Kernel up to 6.12.35/6.15.4/6.16-rc3 HID wacom_aes_battery_handler denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.3$0-$5k0.78

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.12.35/6.15.4/6.16-rc3 and classified as critical. The impacted element is the function wacom_aes_battery_handler of the component HID. The manipulation leads to denial of service. This vulnerability is listed as CVE-2025-38253. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.35/6.15.4/6.16-rc3. It has been rated as critical. This issue affects the function wacom_aes_battery_handler of the component HID. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: fix crash in wacom_aes_battery_handler() Commit fd2a9b29dc9c ("HID: wacom: Remove AES power_supply after extended inactivity") introduced wacom_aes_battery_handler() which is scheduled as a delayed work (aes_battery_work). In wacom_remove(), aes_battery_work is not canceled. Consequently, if the device is removed while aes_battery_work is still pending, then hard crashes or "Oops: general protection fault..." are experienced when wacom_aes_battery_handler() is finally called. E.g., this happens with built-in USB devices after resume from hibernate when aes_battery_work was still pending at the time of hibernation. So, take care to cancel aes_battery_work in wacom_remove().

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-38253 since 04/16/2025. The exploitation is known to be difficult. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 271193 (Ubuntu 24.04 LTS / 25.04 : Linux kernel (Azure) vulnerabilities (USN-7834-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.36, 6.15.5 or 6.16-rc4 eliminates this vulnerability. Applying the patch a4f182ffa30c52ad1c8e12edfb8049ee748c0f1b/57a3d82200dbeccd002244b96acad570eeeb731f/f3054152c12e2eed1e72704aff47b0ea58229584 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (271193), EUVD (EUVD-2025-20808) and CERT Bund (WID-SEC-2025-1517). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Google Cloud Platform
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • NetApp ActiveIQ Unified Manager
  • Dell Avamar
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CNA Base Score: 8.8
CNA Vector (Linux): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 271193
Nessus Name: Ubuntu 24.04 LTS / 25.04 : Linux kernel (Azure) vulnerabilities (USN-7834-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 6.12.36/6.15.5/6.16-rc4
Patch: a4f182ffa30c52ad1c8e12edfb8049ee748c0f1b/57a3d82200dbeccd002244b96acad570eeeb731f/f3054152c12e2eed1e72704aff47b0ea58229584

Timelineinfo

04/16/2025 🔍
07/09/2025 +84 days 🔍
07/09/2025 +0 days 🔍
08/01/2026 +388 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38253 (🔍)
GCVE (CVE): GCVE-0-2025-38253
GCVE (VulDB): GCVE-100-315773
EUVD: 🔍
CERT Bund: WID-SEC-2025-1517 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 07/09/2025 13:56
Updated: 08/01/2026 04:18
Changes: 07/09/2025 13:56 (59), 07/09/2025 15:33 (1), 08/23/2025 03:24 (7), 09/28/2025 11:01 (1), 10/26/2025 07:17 (2), 11/02/2025 22:00 (1), 11/20/2025 00:41 (12), 01/30/2026 22:44 (1), 05/02/2026 16:05 (1), 08/01/2026 04:18 (13)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!