Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-50095

7.8 · HIGH

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…

Published Jun 18, 2025CWE-416EPSS 0.25%

Overview

CVE-2022-50095 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/541840859ace9c2ccebc32fa9e376c7bd3def490Refgit.kernel.org/stable/c/9e255ed238fc67058df87b0388ad6d4b2ef3a2bdRefgit.kernel.org/stable/c/b2fc1723eb65abb83e00d5f011de670296af0b28Refgit.kernel.org/stable/c/e362359ace6f87c201531872486ff295df306d13Refgit.kernel.org/stable/c/e8cb6e8fd9890780f1bfcf5592889e1b879e779c

How CyberStrike helps

Frequently asked questions

What is CVE-2022-50095?

CVE-2022-50095 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-50095?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-50095?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50095?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50095 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999