Security readout for executives and security teams
Plain-English summary
A Linux kernel race can free an RPMsg control-device object while its character-device component is still being released. A local, low-privileged user may potentially trigger memory corruption with serious confidentiality, integrity, and availability consequences. Exposure depends on the affected RPMsg character-device functionality being present and reachable.
Executive priority
Treat as a high-priority local privilege and stability risk on exposed RPMsg-enabled devices. Inventory affected kernels promptly and deploy vendor-corrected builds, while giving lower priority to systems without the relevant functionality or untrusted local access.
Technical view
The rpmsg_ctrldev structure embeds a managed cdev whose release timing is unpredictable. The former teardown path could free the enclosing structure before cdev cleanup completed, creating an unsafe object-lifetime race. The kernel fix replaces separate cdev add/delete handling with cdev_device_add/del(), which coordinates both lifecycles.
Likely exposure
Most relevant to Linux systems running an affected kernel and exposing the RPMsg character-device control path to local users. The supplied version data is ambiguous, so organizations should compare their exact kernel build against the linked stable commits and distribution guidance.
Exploitation context
CVSS 3.1 rates this 7.8: local access, low complexity, low privileges, and no user interaction, with potentially high impact. The supplied record says it is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The evidence establishes a teardown race and premature free condition but provides no CWE, demonstrated exploit chain, or exploitation telemetry. Exact vulnerable ranges are not safely inferable from the supplied version array. Validate exposure through configuration, interface permissions, vendor backports, and commit ancestry rather than version strings alone.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable linked stable fix.
Check distribution or device-vendor guidance for the corrected package and required reboot.
Prioritize systems where local users can reach RPMsg character-device interfaces.
Where updates are delayed, restrict untrusted local access and monitor affected systems.
Validation and detection
Record the running kernel version, distribution package release, and device firmware build.
Determine whether RPMsg character-device support is enabled and reachable by untrusted local users.
Confirm the applicable stable fix is present in the running kernel source or vendor package.
After updating and rebooting, verify the corrected kernel is active.
Review kernel logs for object-lifetime warnings involving rpmsg_ctrldev or cdev cleanup.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48759 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.