CVE-2023-52633

um: time-travel: fix time corruption

MEDIUM
5
CVSS Score
Published: April 2, 2024 at 06:49 AM UTC
Updated: June 17, 2026 at 06:43 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: um: time-travel: fix time corruption In 'basic' time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that's incompatible with the forward, and we'll crash because time goes backwards when we do the forwarding. Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 5.15.1495.16 ≤ v < 6.1.775.3 ≤ v < 5.15.1495.3 ≤ v < 6.1.775.3 ≤ v < 6.6.165.3 ≤ v < 6.7.45.3 ≤ v < 6.86.2 ≤ v < 6.6.166.7 ≤ v < 6.7.45.365038706f77a56754e8f0c2556dab7e22dfe577
Vendor states this is fixed in 0c7478a2da3f5fe106b4658338873d50c86ac7ab (fixed)
Vendor states this is fixed in 4f7dad73df4cdb2b7042103d3922745d040ad025 (fixed)
Vendor states this is fixed in abe4eaa8618bb36c2b33e9cdde0499296a23448c (fixed)
Vendor states this is fixed in b427f55e9d4185f6f17cc1e3296eb8d0c4425283 (fixed)
Vendor states this is fixed in de3e9d8e8d1ae0a4d301109d1ec140796901306c (fixed)
Vendor states this is fixed in 5.15.149 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.77 (unaffected)
Vendor states this is fixed in 6.6.16 (unaffected)
Vendor states this is fixed in 6.7.4 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0c7478a2da3f5fe106b4658338873d50c86ac7ab
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4f7dad73df4cdb2b7042103d3922745d040ad025
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/abe4eaa8618bb36c2b33e9cdde0499296a23448c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b427f55e9d4185f6f17cc1e3296eb8d0c4425283
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/de3e9d8e8d1ae0a4d301109d1ec140796901306c

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card