CVE-2023-53797 json
HID: wacom: Use ktime_t rather than int when dealing with timestamps
published 2025-12-09 11 mo ago modified 2026-08-05 3 mo ago also EUVD-2023-60109
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.4.251, 5.10.188, 5.15.120, 6.1.37, 6.3, 6.3.11, 6.4.1, 6.5
- linux Debian 12 6.1.37-1
- linux Debian 14, Debian 13 6.3.11-1
debian advisories DEBIAN-CVE-2023-53797
- linux Ubuntu 20.04 LTS 5.4.0-166.183
- linux Ubuntu 22.04 LTS 5.15.0-86.96
- linux-aws Ubuntu 20.04 LTS 5.4.0-1113.123
- linux-aws Ubuntu 22.04 LTS 5.15.0-1047.52
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1117.126
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1044.52
- linux-gke Ubuntu 22.04 LTS 5.15.0-1044.49
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1060.65
ubuntu advisories UBUNTU-CVE-2023-53797
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1.21.16
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.28.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.28.1
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0315-1SUSE-SU-2026:0293-1
- git.kernel.org/stable/c/99036f1aed7e82773904f5d91a9897bb3e507fd9 commit
- git.kernel.org/stable/c/9598a647ecc8f300b0540abf9d3b3439859d163b commit
- git.kernel.org/stable/c/67ce7724637c6adb66f788677cb50b82615de0ac commit
- git.kernel.org/stable/c/d89750b19681581796dfbe3689bbb5d439b99b24 commit
- git.kernel.org/stable/c/bdeaa883b765709f231f47f9d6cc76c837a15396 commit
- git.kernel.org/stable/c/d0198363f9108e4adb2511e607ba91e44779e8b1 commit
- git.kernel.org/stable/c/9a6c0e28e215535b2938c61ded54603b4e5814c5 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53797 updated cvss 7.1
kernel: HID: wacom: Use ktime_t rather than int when dealing with timestamps
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/99036f1aed7e82773904f5d91a9897bb3e507fd9
- git.kernel.org /stable/c/9598a647ecc8f300b0540abf9d3b3439859d163b
- git.kernel.org /stable/c/67ce7724637c6adb66f788677cb50b82615de0ac
- git.kernel.org /stable/c/d89750b19681581796dfbe3689bbb5d439b99b24
- git.kernel.org /stable/c/bdeaa883b765709f231f47f9d6cc76c837a15396
- git.kernel.org /stable/c/d0198363f9108e4adb2511e607ba91e44779e8b1
- git.kernel.org /stable/c/9a6c0e28e215535b2938c61ded54603b4e5814c5
Sources
- CVE List CVE-2023-53797
- NVD CVE-2023-53797
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.