# CVE-2023-53797: HID: wacom: Use ktime_t rather than int when dealing with timestamps

> Integer overflow in Wacom HID driver causes incorrect timestamps, leading to potential input handling hangs in userspace.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-53797, DEBIAN-CVE-2023-53797, GHSA-w9q3-wxhm-4gcg, UBUNTU-CVE-2023-53797

## What is CVE-2023-53797?

CVE-2023-53797 is a high-severity vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2023-53797?


## How do I fix CVE-2023-53797?

Apply the vendor's patch.

## Is CVE-2023-53797 being exploited?

There is no known exploitation of CVE-2023-53797 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53797 and fix it if it is affected.

What it is: CVE-2023-53797 is a high-severity vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53797 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-53797/ (Markdown: https://insights.sbomify.com/CVE-2023-53797/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-53797
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-53797
- OSV: https://osv.dev/vulnerability/CVE-2023-53797

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-53797/
Summaries are generated and may contain mistakes; the official description above is the record.