Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53797, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Deferred3.1High7.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS (exploitation in 30 days)
0.32% · top 75% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected f9e27d4bdb1fe257c1453d02560e3adc3e5b6023 – < 99036f1aed7e82773904f5d91a9897bb3e507fd9
    • affected 4502ebbdc0e21e44a8a706428e420ae9c1bb9bba – < 9598a647ecc8f300b0540abf9d3b3439859d163b
    • affected 5047a228d4c8e2b5d1b856f21a00ecf717945a9c – < 67ce7724637c6adb66f788677cb50b82615de0ac
    • affected fb98336e23c11e9c8c7dd5425ec71adbbef7f773 – < d89750b19681581796dfbe3689bbb5d439b99b24
    • affected 694d3e4387bfa69925e075053894385351106e64 – < bdeaa883b765709f231f47f9d6cc76c837a15396
    • affected 17d793f3ed53080dab6bbeabfc82de890c901001 – < d0198363f9108e4adb2511e607ba91e44779e8b1
    • affected 17d793f3ed53080dab6bbeabfc82de890c901001 – < 9a6c0e28e215535b2938c61ded54603b4e5814c5
    • affected 82a136c35506dc788a6c03ffeb11b10c907b0e26
    • affected 5.4.243 – < 5.4.251
    • affected 5.10.180 – < 5.10.188
    • affected 5.15.112 – < 5.15.120
    • affected 6.1.29 – < 6.1.37
    • affected 6.3.3 – < 6.3.11
    • affected 6.2.16 – < 6.3
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 5.4.251 – ≤ 5.4.*
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.120 – ≤ 5.15.*
    • unaffected 6.1.37 – ≤ 6.1.*
    • unaffected 6.3.11 – ≤ 6.3.*
    • unaffected 6.4.1 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53797 badge
[![CVE-2023-53797](https://cveledger.app/badge/CVE-2023-53797.svg)](https://cveledger.app/cve/CVE-2023-53797)

Record last updated .