Possible deadlock in Linux kernel event handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unknown |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Workaround
There is no known mitigation.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3710-1 | linux security update |
Debian DLA |
DLA-3711-1 | linux-5.10 security update |
Debian DSA |
DSA-5594-1 | linux security update |
EUVD |
EUVD-2023-38405 | 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). |
Ubuntu USN |
USN-6461-1 | Linux kernel (OEM) vulnerabilities |
Ubuntu USN |
USN-6624-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-6625-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-6625-2 | Linux kernel (GCP) vulnerabilities |
Ubuntu USN |
USN-6625-3 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-6626-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-6626-2 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-6626-3 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-6628-1 | Linux kernel (Intel IoTG) vulnerabilities |
Ubuntu USN |
USN-6628-2 | Linux kernel (Intel IoTG) vulnerabilities |
Ubuntu USN |
USN-6652-1 | Linux kernel (Azure) vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.152% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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). | 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). |