A flaw was found in the Linux kernel’s io_uring implementation. This flaw allows an attacker with a local account to corrupt system memory, crash the system or escalate privileges.
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://bugzilla.redhat.com/show_bug.cgi?id=1997328 | issue tracking third party advisory |
https://www.zerodayinitiative.com/advisories/ZDI-22-362/ | vdb entry third party advisory |
https://github.com/torvalds/linux/commit/a30f895ad3239f45012e860d4f94c1a388b36d14 | third party advisory patch |
https://access.redhat.com/security/cve/CVE-2022-1043 | third party advisory |
http://packetstormsecurity.com/files/170834/io_uring-Same-Type-Object-Reuse-Privilege-Escalation.html | exploit vdb entry third party advisory |