Local kernel compromise via rpmsg device teardown race
Published Jun 20, 2024 · Updated Aug 5, 2026
A race condition in Linux kernel rpmsg character-device handling allows local users to trigger a use-after-free during device teardown. rpmsg_ctrldev_release_device frees the enclosing control-device structure while its managed cdev can remain active because cdev release timing is not synchronized. A low-privileged local user must be able to race rpmsg character-device teardown; successful exploitation can compromise kernel confidentiality, integrity, and availability.
Summary
What happened
A race condition in Linux kernel rpmsg character-device handling allows local users to trigger a use-after-free during device teardown. rpmsg_ctrldev_release_device frees the enclosing control-device structure while its managed cdev can remain active because cdev release timing is not synchronized. A low-privileged local user must be able to race rpmsg character-device teardown; successful exploitation can compromise kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2022-48759
- Published
- Jun 20, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, CWE-362
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.11
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <1dbb206730f3e5ce90014ad569ddf8167ec4124a
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <70cb4295ec806b663665e1d2ed15caab6159880e
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <74d85e9fbc7022a4011102c7474a9c7aeb704a35
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <85aba11a8ea92a8eef2de95ebbe063086fd62d9c
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <b7fb2dad571d1e21173c06cef0bced77b323990a
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <d6cdc6ae542845d4d0ac8b6d99362bde7042a3c7
- Affected versionversion=c0cdc19f84a4712cf74888f83af286e3c2e14efd <da27b834c1e0222e149e06caddf7718478086d1b
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