CVE-2023-53273

Drivers: vmbus: Check for channel allocation before looking up relids

MEDIUM
5.5
CVSS Score
Published: September 16, 2025 at 08:11 AM UTC
Updated: June 17, 2026 at 06:44 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.1075.16 ≤ v < 6.1.245.8 ≤ v < 5.10.1785.8 ≤ v < 5.15.1075.8 ≤ v < 6.1.245.8 ≤ v < 6.2.115.8 ≤ v < 6.36.2 ≤ v < 6.2.115.86.3 rc16.3 rc26.3 rc36.3 rc46.3 rc58b6a877c060ed6b86878fe66c7c6493a6054cf23
Vendor states this is fixed in 176c6b4889195fbe7016d9401175b48c5c9edf68 (fixed)
Vendor states this is fixed in 1eb65c8687316c65140b48fad27133d583178e15 (fixed)
Vendor states this is fixed in 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee (fixed)
Vendor states this is fixed in a5c44f3446a0565139b7d8abc78f58b86c398123 (fixed)
Vendor states this is fixed in c373e49fbb87aa177819866ed9194ebc5414dfd6 (fixed)
Vendor states this is fixed in 5.10.178 (unaffected)
Vendor states this is fixed in 5.15.107 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.24 (unaffected)
Vendor states this is fixed in 6.2.11 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/176c6b4889195fbe7016d9401175b48c5c9edf68
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1eb65c8687316c65140b48fad27133d583178e15
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a5c44f3446a0565139b7d8abc78f58b86c398123
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c373e49fbb87aa177819866ed9194ebc5414dfd6

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card