HID: wacom: Use ktime_t rather than int when dealing with timestamps
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.251, 5.10.188, 5.15.120, 6.1.37, 6.3.11, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5.4.243 · fixed in 5.4.251; From 5.10.180 · fixed in 5.10.188; From 5.15.112 · fixed in 5.15.120; From 6.1.29 · fixed in 6.1.37; From 6.3.3 · fixed in 6.3.11; From 6.2.16 · fixed in 6.3
- Linux Linux
6.4
References 7
git.kernel.org
- stable/c/99036f1aed7e82773904f5d91a9897bb3e507fd9
- stable/c/9598a647ecc8f300b0540abf9d3b3439859d163b
- stable/c/67ce7724637c6adb66f788677cb50b82615de0ac
- stable/c/d89750b19681581796dfbe3689bbb5d439b99b24
- stable/c/bdeaa883b765709f231f47f9d6cc76c837a15396
- stable/c/d0198363f9108e4adb2511e607ba91e44779e8b1
- stable/c/9a6c0e28e215535b2938c61ded54603b4e5814c5