CVE-2022-50095
Last modified
CVE-2022-50095 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.7, < 5.10.137 |
| Linux | Linux Kernel | >= 5.11, < 5.15.61 |
| Linux | Linux Kernel | >= 5.16, < 5.18.18 |
| Linux | Linux Kernel | >= 5.19, < 5.19.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-50095?
How severe is CVE-2022-50095?
How do I fix CVE-2022-50095?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50089In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50090In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50091In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50092In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50093In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-50094In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-50096In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50097In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50098In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50099In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50101In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2022-50095?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
