CVE-2022-49422: dmaengine: idxd: Fix the error handling path in idxd_cdev_register()
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: Fix the error handling path in idxd_cdev_register()
If a call to alloc_chrdev_region() fails, the already allocated resources
are leaking.
Add the needed error handling path to fix the leak.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49422 is a Linux kernel resource leak in the idxd DMA engine driver error path. If a character device allocation fails during registration, previously allocated resources are not released. Public sources do not provide CVSS, confirmed impact, or active exploitation evidence.
Executive priority
Treat as routine kernel maintenance unless your environment heavily depends on affected idxd functionality. There is no public evidence of active exploitation, but kernel resource leaks can affect stability and should be corrected through normal patch cycles.
Technical view
The issue is in idxd_cdev_register(). When alloc_chrdev_region() fails, the function did not unwind already allocated resources. Kernel stable commits add the missing error handling path. The CVE record lists Linux kernel versions including 5.6, 5.10.121, 5.15.46, 5.17.14, 5.18.3, and 5.19 as affected, but version range details are limited.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with the idxd DMA engine driver code relevant. The available record does not identify distributions, configurations, or whether the driver must be loaded or reachable by unprivileged users.
Exploitation context
No CISA KEV listing or cited source indicates active exploitation. The described condition requires alloc_chrdev_region() failure during idxd character device registration, suggesting reliability and exploitability depend on local kernel state and configuration. Public evidence only supports a resource leak conclusion.
Researcher notes
The public description is narrow: a missing cleanup path after alloc_chrdev_region() failure. No CWE, CVSS, proof of concept, privilege requirement, or distribution matrix is provided. Validate impact against kernel source, backport status, and whether idxd registration failure can be attacker-influenced.
Mitigation direction
Update to a Linux kernel or distribution package containing the referenced stable fix.
Check your Linux vendor advisory for exact affected and fixed package versions.
Prioritize systems using kernels and hardware configurations that enable idxd functionality.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Confirm whether vendor packages include one of the referenced stable commits.
Review kernel configuration or module inventory for idxd driver presence.
Track CVE and vendor advisories for updated severity or impact details.
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-49422 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
6Source 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:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.