Vulnerability · Published Sep 16, 2025 · Assigned by Linux
CVE-2023-53273Drivers: vmbus: Check for channel allocation before looking up relids
Medium 5.5
In plain English
A medium-severity null pointer dereference in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53273 |
| Debian:13 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53273 |
| Debian:14 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux | 5.15.0-79.86 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1042.47 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1045.52 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1045.52.1 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1039.47 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1039.44 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1025.30 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1035.38 | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1037.42 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1039.44 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-79.88 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1030.30 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1016.16 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1002.2 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1040.46 | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1035.38 | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-53273 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-53273 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8b6a877c060ed6b86878fe66c7c6493a6054cf23 – before 176c6b4889195fbe7016d9401175b48c5c9edf688b6a877c060ed6b86878fe66c7c6493a6054cf23 – before c373e49fbb87aa177819866ed9194ebc5414dfd68b6a877c060ed6b86878fe66c7c6493a6054cf23 – before 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee8b6a877c060ed6b86878fe66c7c6493a6054cf23 – before a5c44f3446a0565139b7d8abc78f58b86c3981238b6a877c060ed6b86878fe66c7c6493a6054cf23 – before 1eb65c8687316c65140b48fad27133d583178e15 |
| Linux | Linux | 5.8 |
Weakness: CWE-476 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References
- https://git.kernel.org/stable/c/176c6b4889195fbe7016d9401175b48c5c9edf68
- https://git.kernel.org/stable/c/c373e49fbb87aa177819866ed9194ebc5414dfd6
- https://git.kernel.org/stable/c/8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee
- https://git.kernel.org/stable/c/a5c44f3446a0565139b7d8abc78f58b86c398123
- https://git.kernel.org/stable/c/1eb65c8687316c65140b48fad27133d583178e15