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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.178, 5.15.107, 6.1.24, 6.2.11
- CVEs
- CVE-2023-53273
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 05:26 UTC · Revision 1
Source evidence
Drivers: vmbus: Check for channel allocation before looking up relids
core-osv · Original sourcePublished 16 Sept 2025, 08:11 UTC
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.
osv:CVE-2023-53273
Kernel
Fixed versions: 5.10.178, 5.15.107, 6.1.24, 6.2.11
Complete source record
{
"id": "0fed633cf99dc5b59de5a3bb05d2f4d675ec2ce91dab5e0610b997bcd7626c5f",
"url": "https://osv.dev/vulnerability/CVE-2023-53273",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Drivers: vmbus: Check for channel allocation before looking up relids",
"summary": "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.",
"evidence": "osv:CVE-2023-53273",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.178",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.107",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.24",
"evidence": "/affected/1/ranges"
},
{
"value": "6.2.11",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2023-53273",
"aliases": [
"CVE-2023-53273"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8b6a877c060ed6b86878fe66c7c6493a6054cf23"
},
{
"fixed": "176c6b4889195fbe7016d9401175b48c5c9edf68"
},
{
"fixed": "c373e49fbb87aa177819866ed9194ebc5414dfd6"
},
{
"fixed": "8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee"
},
{
"fixed": "a5c44f3446a0565139b7d8abc78f58b86c398123"
},
{
"fixed": "1eb65c8687316c65140b48fad27133d583178e15"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53273.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.8.0"
},
{
"fixed": "5.10.178"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.107"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.24"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.2.11"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53273.json"
}
}
],
"modified": "2026-10-28T02:30:26.396028684Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/176c6b4889195fbe7016d9401175b48c5c9edf68",
"https://git.kernel.org/stable/c/1eb65c8687316c65140b48fad27133d583178e15",
"https://git.kernel.org/stable/c/8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee",
"https://git.kernel.org/stable/c/a5c44f3446a0565139b7d8abc78f58b86c398123",
"https://git.kernel.org/stable/c/c373e49fbb87aa177819866ed9194ebc5414dfd6",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53273.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53273",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53273.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53273",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 492696,
"published_at": "2025-09-16T08:11:08.792+00:00"
}