LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48950: perf: Fix perf_pending_task() UaF

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety bug in the perf subsystem. A delayed perf task can run after the related event object has been freed, creating a use-after-free condition. The source bundle names stable kernel fixes but does not provide CVSS, CWE, or complete affected version ranges.

Executive priority

Handle through normal kernel patch governance unless vendor advisories raise severity. The missing CVSS and exploitation evidence reduce urgency, but kernel use-after-free bugs still warrant timely remediation on shared or multi-user systems.

Technical view

The flaw is in perf_pending_task() and perf_event lifetime handling. syzbot found task_work could remain queued, or be queued during event teardown, after the perf_event is freed. The kernel fixes extend event lifetime around task_work and avoid queuing task_work while marking the event dead.

Likely exposure

Exposure is limited to Linux kernels containing the affected perf_event code. The bundle does not provide complete vulnerable version ranges. Systems should be assessed by kernel package lineage, distribution advisories, and whether included kernels contain the referenced stable fixes.

Exploitation context

The bundle cites syzbot discovery and kernel stable fixes. It does not cite active exploitation, public exploit use, or CISA KEV listing. Treat exploitation status as not evidenced by the provided sources.

Researcher notes

The key uncertainty is affected-range precision. The bundle lists Linux versions and commit hashes but marks default status as unaffected, so rely on upstream stable commits and distro backport metadata rather than assuming all nearby kernels are vulnerable.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution advisories for CVE-2022-48950 package status.
  • Prioritize systems where untrusted users can exercise perf_event features.
  • Use vendor guidance before changing perf_event access controls.

Validation and detection

  • Inventory deployed Linux kernel versions and package builds.
  • Map each kernel package to the referenced stable commits or vendor backports.
  • Confirm vendor advisories identify the CVE as fixed or not affected.
  • Document any systems still running unverified kernel builds.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48950 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxca7b0a10287e2733bdafb01ef0d4038536625fe3, 078c12ccf1fb943cc18c84894c76113dc89e5975, ca6c21327c6af02b7eec31ce4b9a740a18c6c13funaffected
LinuxLinux5.15.77, 6.0.7unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.