CVE-2023-54024 json
KVM: Destroy target device if coalesced MMIO unregistration fails
published 2025-12-24 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-205132
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Linux Linux 5.4.235, 5.10.173, 5.12, 5.13, 5.15.99, 6.1.16, 6.2.3, 6.3
- linux Debian 14, Debian 13, Debian 12 6.1.20-1
debian advisories DEBIAN-CVE-2023-54024
- linux Ubuntu 20.04 LTS 5.4.0-152.169
- linux Ubuntu 22.04 LTS 5.15.0-75.82
- linux-aws Ubuntu 20.04 LTS 5.4.0-1104.112
- linux-aws Ubuntu 22.04 LTS 5.15.0-1038.43
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1107.116
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1036.44
- linux-gke Ubuntu 22.04 LTS 5.15.0-1036.41
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1051.56
ubuntu advisories UBUNTU-CVE-2023-54024
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-362.8.1.el9_3
- rv RHEL 9 5.14.0-362.8.1.el9_3
- perf RHEL 9 5.14.0-362.8.1.el9_3
- rtla RHEL 9 5.14.0-362.8.1.el9_3
- bpftool RHEL 9 7.2.0-362.8.1.el9_3
- libperf RHEL 9 5.14.0-362.8.1.el9_3
- kernel-rt RHEL 9 5.14.0-362.8.1.el9_3
- kernel-64k RHEL 9 5.14.0-362.8.1.el9_3
red hat advisories RHSA-2023:6583
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.194.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.194.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +3 more 5.14.21-150400.24.194.1.150400.24.98.3
- kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.142.1
- kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.142.1
suse advisories SUSE-SU-2026:0617-1SUSE-SU-2026:0411-1SUSE-SU-2026:0369-1SUSE-SU-2026:0350-1SUSE-SU-2026:0317-1SUSE-SU-2026:0263-1
- git.kernel.org/stable/c/10c2a20d73e99463e69b7e92706791656adc16d7 commit
- git.kernel.org/stable/c/76a9886e1b61ce5592df5ae78a19ed30399ae189 commit
- git.kernel.org/stable/c/999439fd5da5a76253e2f2c37b94204f47d75491 commit
- git.kernel.org/stable/c/ccf6a7fb1aedb1472e1241ee55e4d26b68f8d066 commit
- git.kernel.org/stable/c/fb436dd6914325075f07d19851ab277b7a693ae7 commit
- git.kernel.org/stable/c/b1cb1fac22abf102ffeb29dd3eeca208a3869d54 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54024 updated cvss 5.5
kernel: Linux kernel KVM: Memory leak via coalesced MMIO unregistration failure
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/10c2a20d73e99463e69b7e92706791656adc16d7
- git.kernel.org /stable/c/76a9886e1b61ce5592df5ae78a19ed30399ae189
- git.kernel.org /stable/c/999439fd5da5a76253e2f2c37b94204f47d75491
- git.kernel.org /stable/c/ccf6a7fb1aedb1472e1241ee55e4d26b68f8d066
- git.kernel.org /stable/c/fb436dd6914325075f07d19851ab277b7a693ae7
- git.kernel.org /stable/c/b1cb1fac22abf102ffeb29dd3eeca208a3869d54
Sources
- CVE List CVE-2023-54024
- NVD CVE-2023-54024
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.