CVE-2022-50095

posix-cpu-timers: Cleanup CPU timers before freeing them during exec

HIGH
7.8
CVSS Score
Published: June 18, 2025 at 11:02 AM UTC
Updated: August 5, 2026 at 09:24 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
HIGH7.8
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Cleanup CPU timers before freeing them during exec Commit 55e8c8eb2c7b ("posix-cpu-timers: Store a reference to a pid not a task") started looking up tasks by PID when deleting a CPU timer. When a non-leader thread calls execve, it will switch PIDs with the leader process. Then, as it calls exit_itimers, posix_cpu_timer_del cannot find the task because the timer still points out to the old PID. That means that armed timers won't be disarmed, that is, they won't be removed from the timerqueue_list. exit_itimers will still release their memory, and when that list is later processed, it leads to a use-after-free. Clean up the timers from the de-threaded task before freeing them. This prevents a reported use-after-free.

Affected

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

5.11 ≤ v < 5.15.615.16 ≤ v < 5.18.185.19 ≤ v < 5.19.25.7 ≤ v < 5.10.1375.7 ≤ v < 5.15.615.7 ≤ v < 5.18.185.7 ≤ v < 5.19.25.7 ≤ v < 6.05.755e8c8eb2c7b6bf30e99423ccfe7ca032f498f59
Vendor states this is fixed in 541840859ace9c2ccebc32fa9e376c7bd3def490 (fixed)
Vendor states this is fixed in 9e255ed238fc67058df87b0388ad6d4b2ef3a2bd (fixed)
Vendor states this is fixed in b2fc1723eb65abb83e00d5f011de670296af0b28 (fixed)
Vendor states this is fixed in e362359ace6f87c201531872486ff295df306d13 (fixed)
Vendor states this is fixed in e8cb6e8fd9890780f1bfcf5592889e1b879e779c (fixed)
Vendor states this is fixed in 5.10.137 (unaffected)
Vendor states this is fixed in 5.15.61 (unaffected)
Vendor states this is fixed in 5.18.18 (unaffected)
Vendor states this is fixed in 5.19.2 (unaffected)
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/541840859ace9c2ccebc32fa9e376c7bd3def490
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9e255ed238fc67058df87b0388ad6d4b2ef3a2bd
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b2fc1723eb65abb83e00d5f011de670296af0b28
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e362359ace6f87c201531872486ff295df306d13
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e8cb6e8fd9890780f1bfcf5592889e1b879e779c

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

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