Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53515virtio-mmio: don't break lifecycle of vm_dev

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53515, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 95% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < 97a2d55ead76358245b446efd87818e919196d7a
    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < b788ad3b2468512339c05f23692e36860264e674
    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < 3ff54d904fafabd0912796785e53cce4e69ca123
    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < 5b7d5c2dd664eb8b9a06ecbc06e28d39359c422e
    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < af5818c35173e096085c6ae2e3aac605d3d15e41
    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < 2dcb368fe5a8eee498ca75c93a18ce2f3b0d6a8e
    • affected 7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 – < 55c91fedd03d7b9cf0c5199b2eb12b9b8e95281a
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 4.19.293 – ≤ 4.19.*
    • unaffected 5.4.255 – ≤ 5.4.*
    • unaffected 5.10.192 – ≤ 5.10.*
    • unaffected 5.15.128 – ≤ 5.15.*
    • unaffected 6.1.47 – ≤ 6.1.*
    • unaffected 6.4.12 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53515 badge
[![CVE-2023-53515](https://cveledger.app/badge/CVE-2023-53515.svg)](https://cveledger.app/cve/CVE-2023-53515)

Record last updated .