CVE-2023-21400

In multiple functions of io_uring.c, there is a possible kernel memory corruption due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation.

Weakness

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Affected Software

Extended Description

Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.

Potential Mitigations

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/25.html
• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/27.html

References

• http://packetstormsecurity.com/files/175072/Kernel-Live-Patch-Security-Notice-LSN-0098-1.html
• http://www.openwall.com/lists/oss-security/2023/07/14/2
• http://www.openwall.com/lists/oss-security/2023/07/19/2
• http://www.openwall.com/lists/oss-security/2023/07/19/7
• http://www.openwall.com/lists/oss-security/2023/07/25/7
• https://lists.debian.org/debian-lts-announce/2023/10/msg00027.html
• https://security.netapp.com/advisory/ntap-20240119-0012/
• https://source.android.com/security/bulletin/pixel/2023-07-01
• https://www.debian.org/security/2023/dsa-5480