CVE-2023-53797

HID: wacom: Use ktime_t rather than int when dealing with timestamps

HIGH

7.1

CVSS Score

Published: December 9, 2025 at 12:00 AM UTC

Updated: August 5, 2026 at 10:24 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.1

Exploit prediction

EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktime_t rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktime_t type returned by functions like ktime_get. The int type does not offer enough space to store these values, and attempting to use it is a recipe for problems. In this particular case, overflows would occur when calculating/storing timestamps leading to incorrect values being reported to userspace. In some cases these bad timestamps cause input handling in userspace to appear hung.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 6.2.165.10.180 ≤ v < 5.10.1885.15.112 ≤ v < 5.15.1205.4.243 ≤ v < 5.4.2516.1.29 ≤ v < 6.1.376.2.16 ≤ v < 6.36.3.3 ≤ v < 6.3.116.4 ≤ v < 6.4.16.4 ≤ v < 6.517d793f3ed53080dab6bbeabfc82de890c9010014502ebbdc0e21e44a8a706428e420ae9c1bb9bba5.10.180 5.15.112 5.4.2435047a228d4c8e2b5d1b856f21a00ecf717945a9c6.1.29 6.2.16 6.3.3 6.4694d3e4387bfa69925e075053894385351106e6482a136c35506dc788a6c03ffeb11b10c907b0e26f9e27d4bdb1fe257c1453d02560e3adc3e5b6023fb98336e23c11e9c8c7dd5425ec71adbbef7f773

Vendor states this is fixed in 67ce7724637c6adb66f788677cb50b82615de0ac (fixed)

Vendor states this is fixed in 9598a647ecc8f300b0540abf9d3b3439859d163b (fixed)

Vendor states this is fixed in 99036f1aed7e82773904f5d91a9897bb3e507fd9 (fixed)

Vendor states this is fixed in 9a6c0e28e215535b2938c61ded54603b4e5814c5 (fixed)

Vendor states this is fixed in bdeaa883b765709f231f47f9d6cc76c837a15396 (fixed)

Vendor states this is fixed in d0198363f9108e4adb2511e607ba91e44779e8b1 (fixed)

Vendor states this is fixed in d89750b19681581796dfbe3689bbb5d439b99b24 (fixed)

Vendor states this is fixed in 5.10.188 (unaffected)

Vendor states this is fixed in 5.15.120 (unaffected)

Vendor states this is fixed in 5.4.251 (unaffected)

Vendor states this is fixed in 6.1.37 (unaffected)

Affected range stops below 6.3, so it looks safe — our inference, not a vendor statement