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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025122434-CVE-2023-54024-30aa@gregkh>
Date: Wed, 24 Dec 2025 11:57:08 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54024: KVM: Destroy target device if coalesced MMIO unregistration fails

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

The Linux kernel CVE team has assigned CVE-2023-54024 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.4.119 with commit 7d1bc32d6477ff96a32695ea4be8144e4513ab2d and fixed in 5.4.235 with commit 10c2a20d73e99463e69b7e92706791656adc16d7
	Issue introduced in 5.10.37 with commit 2a20592baff59c5351c5200ec667e1a2aa22af85 and fixed in 5.10.173 with commit 76a9886e1b61ce5592df5ae78a19ed30399ae189
	Issue introduced in 5.13 with commit 5d3c4c79384af06e3c8e25b7770b6247496b4417 and fixed in 5.15.99 with commit 999439fd5da5a76253e2f2c37b94204f47d75491
	Issue introduced in 5.13 with commit 5d3c4c79384af06e3c8e25b7770b6247496b4417 and fixed in 6.1.16 with commit ccf6a7fb1aedb1472e1241ee55e4d26b68f8d066
	Issue introduced in 5.13 with commit 5d3c4c79384af06e3c8e25b7770b6247496b4417 and fixed in 6.2.3 with commit fb436dd6914325075f07d19851ab277b7a693ae7
	Issue introduced in 5.13 with commit 5d3c4c79384af06e3c8e25b7770b6247496b4417 and fixed in 6.3 with commit b1cb1fac22abf102ffeb29dd3eeca208a3869d54
	Issue introduced in 5.11.21 with commit 168e82f640ed1891a700bdb43e37da354b2ab63c
	Issue introduced in 5.12.4 with commit 50cbad42bfea8c052b7ca590bd4126cdc898713c

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-54024
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	virt/kvm/coalesced_mmio.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/10c2a20d73e99463e69b7e92706791656adc16d7
	https://git.kernel.org/stable/c/76a9886e1b61ce5592df5ae78a19ed30399ae189
	https://git.kernel.org/stable/c/999439fd5da5a76253e2f2c37b94204f47d75491
	https://git.kernel.org/stable/c/ccf6a7fb1aedb1472e1241ee55e4d26b68f8d066
	https://git.kernel.org/stable/c/fb436dd6914325075f07d19851ab277b7a693ae7
	https://git.kernel.org/stable/c/b1cb1fac22abf102ffeb29dd3eeca208a3869d54