LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49460: PM / devfreq: rk3399_dmc: Disable edev on remove()

In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: rk3399_dmc: Disable edev on remove() Otherwise we hit an unablanced enable-count when unbinding the DFI device: [ 1279.659119] ------------[ cut here ]------------ [ 1279.659179] WARNING: CPU: 2 PID: 5638 at drivers/devfreq/devfreq-event.c:360 devfreq_event_remove_edev+0x84/0x8c ... [ 1279.659352] Hardware name: Google Kevin (DT) [ 1279.659363] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO BTYPE=--) [ 1279.659371] pc : devfreq_event_remove_edev+0x84/0x8c [ 1279.659380] lr : devm_devfreq_event_release+0x1c/0x28 ... [ 1279.659571] Call trace: [ 1279.659582] devfreq_event_remove_edev+0x84/0x8c [ 1279.659590] devm_devfreq_event_release+0x1c/0x28 [ 1279.659602] release_nodes+0x1cc/0x244 [ 1279.659611] devres_release_all+0x44/0x60 [ 1279.659621] device_release_driver_internal+0x11c/0x1ac [ 1279.659629] device_driver_detach+0x20/0x2c [ 1279.659641] unbind_store+0x7c/0xb0 [ 1279.659650] drv_attr_store+0x2c/0x40 [ 1279.659663] sysfs_kf_write+0x44/0x58 [ 1279.659672] kernfs_fop_write_iter+0xf4/0x190 [ 1279.659684] vfs_write+0x2b0/0x2e4 [ 1279.659693] ksys_write+0x80/0xec [ 1279.659701] __arm64_sys_write+0x24/0x30 [ 1279.659714] el0_svc_common+0xf0/0x1d8 [ 1279.659724] do_el0_svc_compat+0x28/0x3c [ 1279.659738] el0_svc_compat+0x10/0x1c [ 1279.659746] el0_sync_compat_handler+0xa8/0xcc [ 1279.659758] el0_sync_compat+0x188/0x1c0 [ 1279.659768] ---[ end trace cec200e5094155b4 ]---

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

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.
Prepared
Confidence
medium
Sources
9

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5a893e31a636cca3798af2db5aee8d3d144b1e1e, 5a893e31a636cca3798af2db5aee8d3d144b1e1e, 5a893e31a636cca3798af2db5aee8d3d144b1e1e, 5a893e31a636cca3798af2db5aee8d3d144b1e1e, 5a893e31a636cca3798af2db5aee8d3d144b1e1e, 5a893e31a636cca3798af2db5aee8d3d144b1e1e, 5a893e31a636cca3798af2db5aee8d3d144b1e1eunaffected
LinuxLinux4.9, 0, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.