CVE-2023-53273
published 2025-09-16CVE-2023-53273: In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel()…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
4.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
Drivers: vmbus: Check for channel allocation before looking up relids
relid2channel() assumes vmbus channel array to be allocated when called.
However, in cases such as kdump/kexec, not all relids will be reset by the host.
When the second kernel boots and if the guest receives a vmbus interrupt during
vmbus driver initialization before vmbus_connect() is called, before it finishes,
or if it fails, the vmbus interrupt service routine is called which in turn calls
relid2channel() and can cause a null pointer dereference.
Print a warning and error out in relid2channel() for a channel id that's invalid
in the second kernel.
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.25-1 (bookworm) | linux 6.1.25-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8b6a877c060ed6b86878fe66c7c6493a6054cf23 < 176c6b4889195fbe7016d9401175b48c5c9edf68 | 176c6b4889195fbe7016d9401175b48c5c9edf68 |
| linux | linux | >= 8b6a877c060ed6b86878fe66c7c6493a6054cf23 < c373e49fbb87aa177819866ed9194ebc5414dfd6 | c373e49fbb87aa177819866ed9194ebc5414dfd6 |
| linux | linux | >= 8b6a877c060ed6b86878fe66c7c6493a6054cf23 < 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee | 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee |
| linux | linux | >= 8b6a877c060ed6b86878fe66c7c6493a6054cf23 < a5c44f3446a0565139b7d8abc78f58b86c398123 | a5c44f3446a0565139b7d8abc78f58b86c398123 |
| linux | linux | >= 8b6a877c060ed6b86878fe66c7c6493a6054cf23 < 1eb65c8687316c65140b48fad27133d583178e15 | 1eb65c8687316c65140b48fad27133d583178e15 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 5.11 < 5.15.107 | 5.15.107 |
| linux | linux_kernel | >= 5.16 < 6.1.24 | 6.1.24 |
| linux | linux_kernel | >= 5.8 < 5.10.178 | 5.10.178 |
| linux | linux_kernel | >= 6.2 < 6.2.11 | 6.2.11 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: Drivers: vmbus: Check for channel allocation before looking up relids
vendor_redhat·2025-09-16·CVSS 5.5
CVE-2023-53273 [MEDIUM] CWE-476 kernel: Drivers: vmbus: Check for channel allocation before looking up relids
kernel: Drivers: vmbus: Check for channel allocation before looking up relids
In the Linux kernel, the following vulnerability has been resolved:
Drivers: vmbus: Check for channel allocation before looking up relids
relid2channel() assumes vmbus channel array to be allocated when called.
However, in cases such as kdump/kexec, not all relids will be reset by the host.
When the second kernel boots and if the guest receives a vmbus interrupt during
vmbus driver initialization before vmbus_connect() is called, before it finishes,
or if it fails, the vmbus interrupt service routine is called which in turn calls
relid2channel() and can cause a null pointer dereference.
Print a warning and error out in relid2channel() for a channel id that's invalid
in the second kernel.
Package: kernel (Red Ha
Debian
CVE-2023-53273: linux - In the Linux kernel, the following vulnerability has been resolved: Drivers: vm...
vendor_debian·2023·CVSS 5.5
CVE-2023-53273 [MEDIUM] CVE-2023-53273: linux - In the Linux kernel, the following vulnerability has been resolved: Drivers: vm...
In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset by the host. When the second kernel boots and if the guest receives a vmbus interrupt during vmbus driver initialization before vmbus_connect() is called, before it finishes, or if it fails, the vmbus interrupt service routine is called which in turn calls relid2channel() and can cause a null pointer dereference. Print a warning and error out in relid2channel() for a channel id that's invalid in the second kernel.
Scope: local
bookworm: resolved (fixed in 6.1.25-1)
bullseye: resolved (fixed in 5.10.178-1)
forky: res
OSV
CVE-2023-53273: In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channe
osv·2025-09-16·CVSS 5.5
CVE-2023-53273 [MEDIUM] CVE-2023-53273: In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channe
In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset by the host. When the second kernel boots and if the guest receives a vmbus interrupt during vmbus driver initialization before vmbus_connect() is called, before it finishes, or if it fails, the vmbus interrupt service routine is called which in turn calls relid2channel() and can cause a null pointer dereference. Print a warning and error out in relid2channel() for a channel id that's invalid in the second kernel.
GHSA
GHSA-h7h5-4hm9-wwx3: In the Linux kernel, the following vulnerability has been resolved:
Drivers: vmbus: Check for channel allocation before looking up relids
relid2chan
ghsa_unreviewed·2025-09-16
CVE-2023-53273 [MEDIUM] CWE-476 GHSA-h7h5-4hm9-wwx3: In the Linux kernel, the following vulnerability has been resolved:
Drivers: vmbus: Check for channel allocation before looking up relids
relid2chan
In the Linux kernel, the following vulnerability has been resolved:
Drivers: vmbus: Check for channel allocation before looking up relids
relid2channel() assumes vmbus channel array to be allocated when called.
However, in cases such as kdump/kexec, not all relids will be reset by the host.
When the second kernel boots and if the guest receives a vmbus interrupt during
vmbus driver initialization before vmbus_connect() is called, before it finishes,
or if it fails, the vmbus interrupt service routine is called which in turn calls
relid2channel() and can cause a null pointer dereference.
Print a warning and error out in relid2channel() for a channel id that's invalid
in the second kernel.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/176c6b4889195fbe7016d9401175b48c5c9edf68https://git.kernel.org/stable/c/1eb65c8687316c65140b48fad27133d583178e15https://git.kernel.org/stable/c/8c3f0ae5435fd20bb1e3a8308488aa6ac33151eehttps://git.kernel.org/stable/c/a5c44f3446a0565139b7d8abc78f58b86c398123https://git.kernel.org/stable/c/c373e49fbb87aa177819866ed9194ebc5414dfd6
2025-09-16
Published