CVE-2021-46919: dmaengine: idxd: fix wq size store permission state
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: fix wq size store permission state
WQ size can only be changed when the device is disabled. Current code
allows change when device is enabled but wq is disabled. Change the check
to detect device state.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue concerns incorrect state handling in the idxd DMA engine driver. The source says work queue size changes were allowed when the device was still enabled, although they should only occur when the device is disabled. Public sources provided do not describe impact, CVSS severity, or active exploitation.
Executive priority
Handle through routine kernel vulnerability management unless your Linux vendor assigns higher severity. There is no provided evidence of active exploitation or business-critical exposure, but kernel fixes should not be deferred indefinitely on systems using affected versions.
Technical view
The flaw is in dmaengine idxd work queue size storage logic. The vulnerable code checked the work queue disabled state instead of the parent device disabled state, allowing a size change in an invalid device state. Stable kernel commits changed the permission check to use device state.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the idxd dmaengine code present or in use. The bundle lists Linux 5.6, 5.10.32, 5.11.16, and 5.12 among affected records, but does not provide distribution package mappings.
Exploitation context
No cited source states active exploitation, public exploit availability, or KEV listing. The provided description also does not define attacker prerequisites, privilege level, or security impact, so exploitation context remains incomplete.
Researcher notes
The record is sparse: no CVSS, CWE, exploitability details, or impact statement are provided. Analysis should focus on mapping downstream vendor kernels to the three stable commits and determining whether idxd is compiled, loaded, or operationally relevant.
Mitigation direction
Check Linux vendor advisories for a kernel containing the referenced stable fixes.
Prioritize normal kernel update workflows for systems using affected kernel lines.
Confirm distribution backport status before assuming version numbers alone are safe.
If patching is delayed, check vendor guidance for driver-specific mitigations.
Validation and detection
Inventory Linux kernel versions across managed hosts.
Identify systems where the idxd dmaengine driver is present or enabled.
Verify installed kernel packages include the referenced stable commits or vendor backports.
Record exceptions where vendor guidance is unavailable or inconclusive.
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-2021-46919 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.