Kernel memory leak via rpmsg device removal
Published May 17, 2024 · Updated May 11, 2026
Memory leak in Linux kernel rpmsg virtio support allows physically proximate attackers to consume kernel memory through device removal. The rpmsg_probe path allocates driver_override through driver_set_override, but rpmsg_remove omits the corresponding free when the device is removed. Exploitation requires physical access, user interaction, and a removable rpmsg virtio device; repeated probe-and-remove cycles retain 128-byte allocations and can degrade service.
Summary
What happened
Memory leak in Linux kernel rpmsg virtio support allows physically proximate attackers to consume kernel memory through device removal. The rpmsg_probe path allocates driver_override through driver_set_override, but rpmsg_remove omits the corresponding free when the device is removed. Exploitation requires physical access, user interaction, and a removable rpmsg virtio device; repeated probe-and-remove cycles retain 128-byte allocations and can degrade service.
The record
- CVE
- CVE-2023-52670
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.13
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <229ce47cbfdc7d3a9415eb676abbfb77d676cb08
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <2d27a7b19cb354c6d04bcdc9239e261ff29858d6
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <4e6cef3fae5c164968118a13f3fe293700adc81a
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <69ca89d80f2c8a1f5af429b955637beea7eead30
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <9a416d624e5fb7246ea97c11fbfea7e0e27abf43
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <d5362c37e1f8a40096452fc201c30e705750e687
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <dd50fe18c234bd5ff22f658f4d414e8fa8cd6a5d
- Affected versionversion=b0b03b8119633de0649da9bd506e4850c401ff2b <f4bb1d5daf77b1a95a43277268adf0d1430c2346
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo