Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 541840859ace9c2ccebc32fa9e376c7bd3def490, 9e255ed238fc67058df87b0388ad6d4b2ef3a2bd, b2fc1723eb65abb83e00d5f011de670296af0b28.

Low priority for now. Upgrade to Linux Linux 541840859ace9c2ccebc32fa9e376c7bd3def490, 9e255ed238fc67058df87b0388ad6d4b2ef3a2bd, b2fc1723eb65abb83e00d5f011de670296af0b28 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 17th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50095

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.7 and later · before 5.10.137
  • linux linux kernel5.11 and later · before 5.15.61
  • linux linux kernel5.16 and later · before 5.18.18
  • linux linux kernel5.19 and later · before 5.19.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 and later · before 541840859ace9c2ccebc32fa9e376c7bd3def490affected · git
    • 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 and later · before 9e255ed238fc67058df87b0388ad6d4b2ef3a2bdaffected · git
    • 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 and later · before e8cb6e8fd9890780f1bfcf5592889e1b879e779caffected · git
    • 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 and later · before b2fc1723eb65abb83e00d5f011de670296af0b28affected · git
    • 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 and later · before e362359ace6f87c201531872486ff295df306d13affected · git
    • before 5.7not affected · semver
    • 5.10.137 and later · up to and including 5.10.*not affected · semver
    • 5.15.61 and later · up to and including 5.15.*not affected · semver
    • 5.18.18 and later · up to and including 5.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.2-16.0.2-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamperfbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreamperf-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::appstreampython3-perf-debuginfobefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::baseosbpftoolbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::baseoskernelbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::baseoskernel-abi-stablelistsbefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0
Red Hat:enterprise_linux:9::baseoskernel-corebefore 0:5.14.0-70.30.1.el9_00:5.14.0-70.30.1.el9_0

+14

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50093Jun 18, 2025 · iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE)
    28Monitor
  • ← EarlierCVE-2022-50094Jun 18, 2025 · spmi: trace: fix stack-out-of-bound access in SPMI tracing functions
    28Monitor
  • Later →CVE-2022-50096Jun 18, 2025 · x86/kprobes: Update kcb status flag after singlestepping
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux541840859ace9c2ccebc32fa9e376c7bd3def490Vendor (CNA)
Linux Linux9e255ed238fc67058df87b0388ad6d4b2ef3a2bdVendor (CNA)
Linux Linuxb2fc1723eb65abb83e00d5f011de670296af0b28Vendor (CNA)
Linux Linuxe362359ace6f87c201531872486ff295df306d13Vendor (CNA)
Linux Linuxe8cb6e8fd9890780f1bfcf5592889e1b879e779cVendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-x86_640:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-devel0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-devel-matched0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-doc0:5.14.0-70.30.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records