A memory leak flaw was found in the Linux kernel’s io_uring functionality in how a user registers a buffer ring with IORING_REGISTER_PBUF_RING, mmap() it, and then frees it. This flaw allows a local user to crash or potentially escalate their privileges on the system.
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-2024-0582 | third party advisory vdb entry |
https://bugs.chromium.org/p/project-zero/issues/detail?id=2504 | issue tracking mailing list |
https://bugzilla.redhat.com/show_bug.cgi?id=2254050 | patch third party advisory issue tracking |
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c392cbecd8eca4c53f2bf508731257d9d0a21c2d | patch mailing list |
http://www.openwall.com/lists/oss-security/2024/04/24/3 |