CVE-2023-53273
Last modified
CVE-2023-53273 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.8, < 5.10.178 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.107 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.24 | — |
| Linux | Linux Kernel | >= 6.2, < 6.2.11 | — |
| Linux | Linux Kernel | 6.3 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53273?
How severe is CVE-2023-53273?
How do I fix CVE-2023-53273?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53268In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53269In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5327A vulnerability was found in SATO CL4NX-J Plus 1.13.2-u455_r…6.5
- CVE-2023-53270In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53271In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53272In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53274In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53275In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53276In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53277In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53278In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53279In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53273?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
