Concurrent removals of certain anonymous shared memory...
Critical severity
Unreviewed
Published
Sep 5, 2024
to the GitHub Advisory Database
•
Updated Sep 5, 2024
Description
Published by the National Vulnerability Database
Sep 5, 2024
Published to the GitHub Advisory Database
Sep 5, 2024
Last updated
Sep 5, 2024
Concurrent removals of certain anonymous shared memory mappings by using the UMTX_SHM_DESTROY sub-request of UMTX_OP_SHM can lead to decreasing the reference count of the object representing the mapping too many times, causing it to be freed too early.
A malicious code exercizing the UMTX_SHM_DESTROY sub-request in parallel can panic the kernel or enable further Use-After-Free attacks, potentially including code execution or Capsicum sandbox escape.
References