CVE-2023-53797
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A Linux kernel HID wacom driver bug uses int instead of ktime_t for timestamps, causing overflow, causing incorrect timestamps and potential userspace input hangs.
Vulnerability
In the Linux kernel's HID subsystem, the Wacom driver incorrectly used the int type to store timestamps returned by functions like ktime_get. The int type lacks sufficient range to hold these values, leading to integer overflows when calculating or storing timestamps [1]. This is a type-mismatch bug that results in corrupted timestamp data being reported to userspace.
Exploitation
The vulnerability is triggered through normal interaction with a Wacom tablet device. No special privileges or authentication are required; the bug manifests whenever the driver processes input events and attempts to compute timestamps. The overflow occurs automatically during standard operation, affecting any system using the affected kernel versions with the vulnerable driver code.
Impact
Due to the overflow, userspace receives incorrect timestamp values. In some cases, these bad timestamps cause input handling in userspace to appear hung, effectively disrupting the user's ability to interact with the system through the tablet [1]. The impact is limited to denial of service (input unresponsiveness) and does not allow arbitrary code execution or privilege escalation.
Mitigation
The fix was applied in the Linux kernel stable tree via commits that replace the int timestamp storage with the proper ktime_t type [1][2][3]. Users should update to a kernel version containing these patches. No workaround is available other than applying the kernel update.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
799036f1aed7e9598a647ecc867ce7724637cd89750b19681bdeaa883b765d0198363f9109a6c0e28e215Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/67ce7724637c6adb66f788677cb50b82615de0acnvd
- git.kernel.org/stable/c/9598a647ecc8f300b0540abf9d3b3439859d163bnvd
- git.kernel.org/stable/c/99036f1aed7e82773904f5d91a9897bb3e507fd9nvd
- git.kernel.org/stable/c/9a6c0e28e215535b2938c61ded54603b4e5814c5nvd
- git.kernel.org/stable/c/bdeaa883b765709f231f47f9d6cc76c837a15396nvd
- git.kernel.org/stable/c/d0198363f9108e4adb2511e607ba91e44779e8b1nvd
- git.kernel.org/stable/c/d89750b19681581796dfbe3689bbb5d439b99b24nvd
News mentions
0No linked articles in our index yet.