{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2022-48950", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-08-22T01:27:53.625Z", "datePublished": "2024-10-21T20:05:38.440Z", "dateUpdated": "2026-08-05T08:53:05.541Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T08:53:05.541Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix perf_pending_task() UaF\n\nPer syzbot it is possible for perf_pending_task() to run after the\nevent is free()'d. There are two related but distinct cases:\n\n - the task_work was already queued before destroying the event;\n - destroying the event itself queues the task_work.\n\nThe first cannot be solved using task_work_cancel() since\nperf_release() itself might be called from a task_work (____fput),\nwhich means the current->task_works list is already empty and\ntask_work_cancel() won't be able to find the perf_pending_task()\nentry.\n\nThe simplest alternative is extending the perf_event lifetime to cover\nthe task_work.\n\nThe second is just silly, queueing a task_work while you know the\nevent is going away makes no sense and is easily avoided by\nre-arranging how the event is marked STATE_DEAD and ensuring it goes\nthrough STATE_OFF on the way down." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The vulnerable path is reached via the local perf_event_open(2) syscall and subsequent event close/release; it is not reachable from the network stack or remote protocols.\nAC:L - An attacker fully controls event creation, overflow/sigtrap triggering, and close/destroy; destroying an event with pending_sigtrap itself queues perf_pending_task then frees the object, so the UAF does not depend on conditions outside attacker influence.\nPR:L - Unprivileged users can open sampling events with attr.sigtrap on their own tasks because ptrace_may_access succeeds for same_thread_group self-access, and default perf_event_paranoid still allows self-monitoring with exclude_kernel.\nUI:N - Exploitation requires only the attacker's own syscalls (perf_event_open, activity to overflow, close/exit); no victim user action is needed.\nS:U - Impact is confined to the local kernel privilege boundary (standard local privilege escalation); this is not a VM escape, IOMMU bypass, or other cross-authority boundary.\nC:H - This is a use-after-free of a large perf_event slab object (~1.4KB); after free, perf_pending_task/perf_sigtrap dereference attacker-sprayable memory, enabling arbitrary kernel read primitives.\nI:H - The same UAF provides a write/control-flow hijack surface via heap reuse of the freed perf_event (including callback_head and ctx pointer use), enabling arbitrary kernel write and code execution.\nA:H - The UAF reliably causes kernel oops/panic (demonstrated by syzbot KASAN crashes in task_work_run/perf_pending_task), fully impacting system availability." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "kernel/events/core.c" ], "versions": [ { "version": "ca7b0a10287e2733bdafb01ef0d4038536625fe3", "lessThan": "8bffa95ac19ff27c8261904f89d36c7fcf215d59", "status": "affected", "versionType": "git" }, { "version": "078c12ccf1fb943cc18c84894c76113dc89e5975", "lessThan": "78e1317a174edbfd1182599bf76c092a2877672c", "status": "affected", "versionType": "git" }, { "version": "ca6c21327c6af02b7eec31ce4b9a740a18c6c13f", "lessThan": "517e6a301f34613bff24a8e35b5455884f2d83d8", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "kernel/events/core.c" ], "versions": [ { "version": "5.15.77", "lessThan": "5.15.84", "status": "affected", "versionType": "semver" }, { "version": "6.0.7", "lessThan": "6.0.14", "status": "affected", "versionType": "semver" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.15.77", "versionEndExcluding": "5.15.84" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.0.7", "versionEndExcluding": "6.0.14" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/8bffa95ac19ff27c8261904f89d36c7fcf215d59" }, { "url": "https://git.kernel.org/stable/c/78e1317a174edbfd1182599bf76c092a2877672c" }, { "url": "https://git.kernel.org/stable/c/517e6a301f34613bff24a8e35b5455884f2d83d8" } ], "title": "perf: Fix perf_pending_task() UaF", "x_generator": { "engine": "bippy-1.2.0" } }, "adp": [ { "metrics": [ { "other": { "type": "ssvc", "content": { "id": "CVE-2022-48950", "role": "CISA Coordinator", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "version": "2.0.3", "timestamp": "2024-10-22T13:21:45.788376Z" } } } ], "title": "CISA ADP Vulnrichment", "providerMetadata": { "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-10-22T13:28:40.788Z" } } ] } }