perf: Fix race between perf_event_exit_task() and perf_pending_task()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: perf: Fix race between perf_event_exit_task() and perf_pending_task() A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec(). During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current). Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 97ba62b278674293762c3d91f724f1bb922f04e0 · fixed in 655acfa713bce9ae9c81a654459890c2f58cb4e8; From 97ba62b278674293762c3d91f724f1bb922f04e0 · fixed in 672b8a9ce8f51b991481dfde26fba5cc4340a91a; From 97ba62b278674293762c3d91f724f1bb922f04e0 · fixed in 524063fea29f8a841e49927ea7a8085194ad3ec2; From 97ba62b278674293762c3d91f724f1bb922f04e0 · fixed in 81e61e3f8befa1bae3ec8e779d8ada5e5e362c21; From 97ba62b278674293762c3d91f724f1bb922f04e0 · fixed in ffb684f2aa141eeb0caa6308422e7e05d1ded7c4
- Linux Linux
5.13
- KernelLinux
From 5.13.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10