Review reviewHigh

CVE-2022-48950

Linux Linux, linux kernel

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()...

CVSS
7.8
EPSS
0.25%
16.5% percentile
CISA KEV
Not listed
Published
2024.10.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.25%
Technical severityCVSS 7.8

Vulnerability overview

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()...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= ca7b0a10287e2733bdafb01ef0d4038536625fe3 < 8bffa95ac19ff27c8261904f89d36c7fcf215d59, >= 078c12ccf1fb943cc18c84894c76113dc89e5975 < 78e1317a174edbfd1182599bf76c092a2877672c, >= ca6c21327c6af02b7eec31ce4b9a740a18c6c13f < 517e6a301f34613bff24a8e35b5455884f2d83d8, >= 5.15.77 < 5.15.84, >= 6.0.7 < 6.0.14, < 5.15.84, >= 5.16 < 6.0.14, 6.1
Fixed versions
5.15.84, 6.0.14

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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