Security readout for executives and security teams
Plain-English summary
CVE-2022-49460 is a Linux kernel bug in the Rockchip RK3399 devfreq memory-controller driver. The source shows a warning triggered when unbinding the DFI device because an event device was not disabled during removal. No source in the bundle shows active exploitation, privilege escalation, data theft, or remote attack impact.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency, unless your fleet includes RK3399-based devices or custom kernels. Prioritize inventory and patch confirmation because the public data lacks severity scoring and exploit evidence.
Technical view
The fix changes the rk3399_dmc devfreq driver to disable the devfreq event device during remove(). Without that cleanup, unbinding the DFI device can leave an unbalanced enable count and trigger a kernel warning in devfreq_event_remove_edev(). Evidence is limited to Linux kernel CVE data and stable commit references.
Likely exposure
Exposure appears limited to Linux systems using the Rockchip RK3399 DMC/devfreq path, such as RK3399-based devices. Generic Linux servers without this hardware/driver path are unlikely to be exposed based on the provided sources.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. The described trigger is device unbinding and cleanup behavior, not a documented remote or unauthenticated attack path.
Researcher notes
Do not generalize this across all Linux deployments. The provided trace points to a lifecycle cleanup bug in drivers/devfreq/rk3399_dmc around DFI device unbinding. Impact, exploitability, and attacker prerequisites are not established in the source bundle.
Mitigation direction
Identify RK3399-based Linux devices and kernel versions in use.
Apply a vendor kernel update containing the referenced stable fix.
For custom kernels, review whether the stable commit was backported.
Follow Linux distribution or device-vendor advisories for supported packages.
Avoid ad hoc driver unbinding on production devices unless operationally required.
Validation and detection
Check whether affected assets use Rockchip RK3399 hardware.
Confirm the running kernel includes the rk3399_dmc remove() fix.
Review kernel logs for devfreq_event_remove_edev warnings during driver unbind tests.
Map deployed versions against vendor fixed kernel packages.
Document any unsupported custom kernels needing backport review.
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-49460 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.
0CVSS vectors
3Timeline events
0ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 26, 2025, 02:13 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.