CVE-2023-34324: Possible deadlock in Linux kernel event handling
Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest.
The closing of an event channel is e.g. triggered by removal of a paravirtual device on the other side. As this action will cause console messages to be issued on the other side quite often, the chance of triggering the deadlock is not neglectable.
Note that 32-bit Arm-guests are not affected, as the 32-bit Linux kernel on Arm doesn't use queued-RW-locks, which are required to trigger the issue (on Arm32 a waiting writer doesn't block further readers to get the lock).
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2023-34324?
CVE-2023-34324 is classified as a medium severity vulnerability due to potential deadlock scenarios in the Linux kernel.
How do I fix CVE-2023-34324?
To mitigate CVE-2023-34324, upgrade to a fixed version of the Linux kernel listed, such as 5.10.223-1 or 6.12.12-1.
Which systems are affected by CVE-2023-34324?
CVE-2023-34324 affects the Linux kernel versions up to 5.10 and the Xen hypervisor.
Is CVE-2023-34324 exploitable remotely?
CVE-2023-34324 does not appear to be directly exploitable remotely as it involves deadlock situations in an unprivileged guest context.
What causes the deadlock in CVE-2023-34324?
The deadlock in CVE-2023-34324 occurs when closing an event channel in parallel with an unrelated Xen console action.