CVE-2022-50095
posix-cpu-timers: Cleanup CPU timers before freeing them during exec
- Published
- Updated
- Reserved
- Assigned by
- Linux
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.
Timeline
ID reserved
By Linux
Published
- 14 months later
· 14 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (8 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 – < 541840859ace9c2ccebc32fa9e376c7bd3def490
- affected 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 – < 9e255ed238fc67058df87b0388ad6d4b2ef3a2bd
- affected 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 – < e8cb6e8fd9890780f1bfcf5592889e1b879e779c
- affected 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 – < b2fc1723eb65abb83e00d5f011de670296af0b28
- affected 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 – < e362359ace6f87c201531872486ff295df306d13
- affected 5.7
- unaffected < 5.7
- unaffected 5.10.137 – ≤ 5.10.*
- unaffected 5.15.61 – ≤ 5.15.*
- unaffected 5.18.18 – ≤ 5.18.*
- unaffected 5.19.2 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References (5)
- https://git.kernel.org/stable/c/541840859ace9c2ccebc32fa9e376c7bd3def490 (opens in a new tab)
- https://git.kernel.org/stable/c/9e255ed238fc67058df87b0388ad6d4b2ef3a2bd (opens in a new tab)
- https://git.kernel.org/stable/c/e8cb6e8fd9890780f1bfcf5592889e1b879e779c (opens in a new tab)
- https://git.kernel.org/stable/c/b2fc1723eb65abb83e00d5f011de670296af0b28 (opens in a new tab)
- https://git.kernel.org/stable/c/e362359ace6f87c201531872486ff295df306d13 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50095)Record last updated .