CVE-2023-53515
BaseFortify
Publication date: 2025-10-01
Last updated on: 2026-04-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's virtio-mmio component involves improper management of the lifecycle of the vm_dev structure. The vm_dev has its own lifecycle because it contains an embedded 'struct device' and requires a release callback to manage its memory correctly. However, the vulnerability arises because vm_dev was allocated using devres, which causes its memory to be freed prematurely when the platform_device is removed, instead of waiting for the vm_dev release callback. This leads to a use-after-free condition when the callback is eventually called.
How can this vulnerability impact me? :
This vulnerability can lead to a use-after-free condition in the Linux kernel, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges by exploiting the freed memory.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by compiling the Linux kernel with the CONFIG_DEBUG_KOBJECT_RELEASE option enabled and then unbinding the device using sysfs to observe the use-after-free behavior.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to apply the fix which avoids using devres for vm_dev and ensures the vm_dev release callback lifecycle is correctly handled. This involves updating the kernel to a version where this issue is resolved.