CVE-2025-38253 [Medium] | Security Vulnerability in Linux Kernel

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().

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-07-09	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-07-09

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-38253

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-38253 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-38253
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-38253
`suse`	medium	CVE-2025-38253 severity moderate: SUSE including 94 source package names (cluster-md-kmp-64kb-6.12.0-160000.6.1, cluster-md-kmp-default, …), 481 product×package rows across 86 product lines (Image SLES-Azure-3P, Image SLES-Azure-Basic, … (86 product lines)): Known Not Affected 283, Fixed 177, First Fixed 21.	https://www.suse.com/security/cve/CVE-2025-38253/
`ubuntu`	medium	CVE-2025-38253 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1548 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1142, ignored 164, released 138, not-affected 99, needed 2, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-38253

Affected software / configurations for CVE-2025-38253

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.8, < 6.12.36	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.15.5	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.16	cpe:2.3:o:linux:linux_kernel:6.16:rc1::::::
linux	linux_kernel	6.16	cpe:2.3:o:linux:linux_kernel:6.16:rc2::::::
linux	linux_kernel	6.16	cpe:2.3:o:linux:linux_kernel:6.16:rc3::::::

References for CVE-2025-38253

URL	Tags
https://git.kernel.org/stable/c/57a3d82200dbeccd002244b96acad570eeeb731f	Patch
https://git.kernel.org/stable/c/a4f182ffa30c52ad1c8e12edfb8049ee748c0f1b	Patch
https://git.kernel.org/stable/c/f3054152c12e2eed1e72704aff47b0ea58229584	Patch

URL

CVE-2025-38253 | HID: wacom: fix crash in wacom_aes_battery_handler()

Exploit prediction scoring system (EPSS) score for CVE-2025-38253

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38253

Weakness enumeration for CVE-2025-38253

OS Trackers for CVE-2025-38253

Affected software / configurations for CVE-2025-38253

References for CVE-2025-38253