drm/amdkfd: hold event_mutex while checkpointing CRIU events
- 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.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: hold event_mutex while checkpointing CRIU events kfd_criu_checkpoint_events() counts the entries in p->event_idr via kfd_get_num_events(), allocates an array sized to that count, and then walks the same IDR to fill it. Neither the count nor the walk holds p->event_mutex. The CRIU checkpoint caller holds only p->mutex. Event create and destroy (kfd_event_create()/kfd_event_destroy()) take p->event_mutex and do not take p->mutex, so a second thread in the same process can insert or remove events between the count and the walk. If an event is inserted, the walk iterates more entries than were counted and writes past the end of the ev_privs allocation; if an event is removed, the walk dereferences an entry that is being freed. Hold p->event_mutex across the count and the walk so both observe a consistent view of p->event_idr. The lock is released before copy_to_user(), which only touches the local buffer. The caller already holds p->mutex and the create/destroy paths never take p->mutex, so the p->mutex -> p->event_mutex order is not inverted and no deadlock is introduced. (cherry picked from commit ff57e223ab105795b05d3ef3f3c35a5a441bcbaa)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 40e8a766a761f7fdc8530347527b344fddf6f1a8 · fixed in 8f7196f25b14f4290738639a50459b56a5ff2784; From 40e8a766a761f7fdc8530347527b344fddf6f1a8 · fixed in 2040b7e39027cb83bb8c7b84a4c95c2f6053c32f; From 40e8a766a761f7fdc8530347527b344fddf6f1a8 · fixed in 9a7f765985f64fd4a7a58f7bc9cd80a1f4230628; From 40e8a766a761f7fdc8530347527b344fddf6f1a8 · fixed in 6a52f48157fa7fb81e0c146937fd6c8b0c1cfdbd; From 40e8a766a761f7fdc8530347527b344fddf6f1a8 · fixed in bed80be08c0bee47fa242a4256ac873477c815f8; From 40e8a766a761f7fdc8530347527b344fddf6f1a8 · fixed in ff8bc5a68a9a70bdc38d61a72c7a49c56063f9d2
- Linux Linux
5.18
- KernelLinux
From 5.18.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.151; From 6.7.0 · fixed in 6.12.103; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8