LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54024: KVM: Destroy target device if coalesced MMIO unregistration fails

In the Linux kernel, the following vulnerability has been resolved: KVM: Destroy target device if coalesced MMIO unregistration fails Destroy and free the target coalesced MMIO device if unregistering said device fails. As clearly noted in the code, kvm_io_bus_unregister_dev() does not destroy the target device. BUG: memory leak unreferenced object 0xffff888112a54880 (size 64): comm "syz-executor.2", pid 5258, jiffies 4297861402 (age 14.129s) hex dump (first 32 bytes): 38 c7 67 15 00 c9 ff ff 38 c7 67 15 00 c9 ff ff 8.g.....8.g..... e0 c7 e1 83 ff ff ff ff 00 30 67 15 00 c9 ff ff .........0g..... backtrace: [<0000000006995a8a>] kmalloc include/linux/slab.h:556 [inline] [<0000000006995a8a>] kzalloc include/linux/slab.h:690 [inline] [<0000000006995a8a>] kvm_vm_ioctl_register_coalesced_mmio+0x8e/0x3d0 arch/x86/kvm/../../../virt/kvm/coalesced_mmio.c:150 [<00000000022550c2>] kvm_vm_ioctl+0x47d/0x1600 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3323 [<000000008a75102f>] vfs_ioctl fs/ioctl.c:46 [inline] [<000000008a75102f>] file_ioctl fs/ioctl.c:509 [inline] [<000000008a75102f>] do_vfs_ioctl+0xbab/0x1160 fs/ioctl.c:696 [<0000000080e3f669>] ksys_ioctl+0x76/0xa0 fs/ioctl.c:713 [<0000000059ef4888>] __do_sys_ioctl fs/ioctl.c:720 [inline] [<0000000059ef4888>] __se_sys_ioctl fs/ioctl.c:718 [inline] [<0000000059ef4888>] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:718 [<000000006444fa05>] do_syscall_64+0x9f/0x4e0 arch/x86/entry/common.c:290 [<000000009a4ed50b>] entry_SYSCALL_64_after_hwframe+0x49/0xbe BUG: leak checking failed

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel KVM memory leak bug. If part of KVM coalesced MMIO cleanup fails, the kernel may leave an allocated device object behind. The source does not show code execution, privilege escalation, or active exploitation. Business urgency is mainly for Linux virtualization hosts that expose or rely on KVM.

Executive priority

Treat as routine kernel hygiene unless you operate shared or multi-tenant KVM infrastructure. There is no supplied evidence of active exploitation or severe impact, but unpatched virtualization hosts should still move through normal kernel update cycles.

Technical view

The resolved flaw is in KVM coalesced MMIO handling. kvm_io_bus_unregister_dev() may fail without destroying the target device, and the old path did not free that object. The supplied trace shows a leak from kvm_vm_ioctl_register_coalesced_mmio() through KVM VM ioctl handling. Stable kernel commits implement cleanup when unregistration fails.

Likely exposure

Most relevant to Linux systems using KVM virtualization, especially hosts on affected kernel branches or unpatched downstream builds. The source bundle lists Linux as affected and provides fixed stable commits, but does not identify specific distributions or packaged kernel versions.

Exploitation context

The record is not in KEV, and the supplied sources do not claim active exploitation. Evidence is a syzkaller-style memory leak report and kernel fix references. The bundle does not establish remote reachability, privilege requirements, or a practical denial-of-service threshold.

Researcher notes

Analysis should focus on the failure path in coalesced MMIO registration and whether downstream trees backported the cleanup. The source bundle only supports a memory leak conclusion; avoid expanding impact without vendor or kernel maintainer evidence.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable KVM fix.
  • Check your distribution kernel advisory for CVE-2023-54024 coverage.
  • Prioritize KVM virtualization hosts and systems allowing VM management access.
  • Track vendor guidance if running custom or long-term kernel builds.

Validation and detection

  • Inventory Linux kernel versions on KVM-capable hosts.
  • Confirm whether installed kernels include one of the referenced stable commits.
  • Review distro CVE notes for fixed package versions.
  • Check whether KVM modules and VM management interfaces are in use.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54024 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7d1bc32d6477ff96a32695ea4be8144e4513ab2d, 2a20592baff59c5351c5200ec667e1a2aa22af85, 5d3c4c79384af06e3c8e25b7770b6247496b4417, 5d3c4c79384af06e3c8e25b7770b6247496b4417, 5d3c4c79384af06e3c8e25b7770b6247496b4417, 5d3c4c79384af06e3c8e25b7770b6247496b4417, 168e82f640ed1891a700bdb43e37da354b2ab63c, 50cbad42bfea8c052b7ca590bd4126cdc898713c, 5.4.119, 5.10.37, 5.11.21, 5.12.4unaffected
LinuxLinux5.13, 0, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.