7.8

CVE-2023-53515

In the Linux kernel, the following vulnerability has been resolved:

virtio-mmio: don't break lifecycle of vm_dev

vm_dev has a separate lifecycle because it has a 'struct device'
embedded. Thus, having a release callback for it is correct.

Allocating the vm_dev struct with devres totally breaks this protection,
though. Instead of waiting for the vm_dev release callback, the memory
is freed when the platform_device is removed. Resulting in a
use-after-free when finally the callback is to be called.

To easily see the problem, compile the kernel with
CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs.

The fix is easy, don't use devres in this case.

Found during my research about object lifetime problems.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
LinuxLinux Kernel Version >= 4.15.1 < 4.19.293
LinuxLinux Kernel Version >= 4.20 < 5.4.255
LinuxLinux Kernel Version >= 5.5 < 5.10.192
LinuxLinux Kernel Version >= 5.11 < 5.15.128
LinuxLinux Kernel Version >= 5.16 < 6.1.47
LinuxLinux Kernel Version >= 6.2 < 6.4.12
LinuxLinux Kernel Version4.15 Update-
LinuxLinux Kernel Version4.15 Updaterc3
LinuxLinux Kernel Version4.15 Updaterc4
LinuxLinux Kernel Version4.15 Updaterc5
LinuxLinux Kernel Version4.15 Updaterc6
LinuxLinux Kernel Version4.15 Updaterc7
LinuxLinux Kernel Version4.15 Updaterc8
LinuxLinux Kernel Version4.15 Updaterc9
LinuxLinux Kernel Version6.5 Updaterc1
LinuxLinux Kernel Version6.5 Updaterc2
LinuxLinux Kernel Version6.5 Updaterc3
LinuxLinux Kernel Version6.5 Updaterc4
LinuxLinux Kernel Version6.5 Updaterc5
LinuxLinux Kernel Version6.5 Updaterc6
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.02% 0.054
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
nvd@nist.gov 7.8 1.8 5.9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.