A use-after-free flaw was found in mm/mempolicy.c in the memory management subsystem in the Linux Kernel. This issue is caused by a race between mbind() and VMA-locked page fault, and may allow a local attacker to crash the system or lead to a kernel information leak.
Workaround:
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://access.redhat.com/security/cve/CVE-2023-4611 | third party advisory vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2227244 | patch third party advisory issue tracking |
https://www.spinics.net/lists/stable-commits/msg310136.html | patch mailing list |