CVE-2023-53797 — HID: wacom: Use ktime_t rather than int when dealing with timestamps
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f9e27d4bdb1fe257c1453d02560e3adc3e5b6023 and < 99036f1aed7e82773904f5d91a9897bb3e507fd9≥ 4502ebbdc0e21e44a8a706428e420ae9c1bb9bba and < 9598a647ecc8f300b0540abf9d3b3439859d163b≥ 5047a228d4c8e2b5d1b856f21a00ecf717945a9c and < 67ce7724637c6adb66f788677cb50b82615de0ac≥ fb98336e23c11e9c8c7dd5425ec71adbbef7f773 and < d89750b19681581796dfbe3689bbb5d439b99b24≥ 694d3e4387bfa69925e075053894385351106e64 and < bdeaa883b765709f231f47f9d6cc76c837a15396≥ 17d793f3ed53080dab6bbeabfc82de890c901001 and < d0198363f9108e4adb2511e607ba91e44779e8b1≥ 17d793f3ed53080dab6bbeabfc82de890c901001 and < 9a6c0e28e215535b2938c61ded54603b4e5814c5version 82a136c35506dc788a6c03ffeb11b10c907b0e26 and 7 more≥ 5.4.243 and < 5.4.251≥ 5.10.180 and < 5.10.188≥ 5.15.112 and < 5.15.120≥ 6.1.29 and < 6.1.37≥ 6.3.3 and < 6.3.11≥ 6.2.16 and < 6.3version 6.4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | High | 2.8 | 4.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.1 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.30%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.1
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- git.kernel.org/stable/c/67ce7724637c6adb66f788677cb50b82615de0ac
- git.kernel.org/stable/c/9598a647ecc8f300b0540abf9d3b3439859d163b
- git.kernel.org/stable/c/d0198363f9108e4adb2511e607ba91e44779e8b1
- git.kernel.org/stable/c/d89750b19681581796dfbe3689bbb5d439b99b24
- git.kernel.org/stable/c/bdeaa883b765709f231f47f9d6cc76c837a15396
- git.kernel.org/stable/c/9a6c0e28e215535b2938c61ded54603b4e5814c5
- git.kernel.org/stable/c/99036f1aed7e82773904f5d91a9897bb3e507fd9
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 14h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 14h
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-53797 is "HID: wacom: Use ktime_t rather than int when dealing with timestamps", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.