LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47003: dmaengine: idxd: Fix potential null dereference on pointer status

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix potential null dereference on pointer status There are calls to idxd_cmd_exec that pass a null status pointer however a recent commit has added an assignment to *status that can end up with a null pointer dereference. The function expects a null status pointer sometimes as there is a later assignment to *status where status is first null checked. Fix the issue by null checking status before making the assignment. Addresses-Coverity: ("Explicit null dereferenced")

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-47003 is a Linux kernel bug in the idxd DMA engine driver. A code path could dereference a null status pointer. The public record does not provide a CVSS score, confirmed exploitability, or business impact details, so urgency depends on whether affected kernels and this driver are present.

Executive priority

Handle through normal kernel patch management unless affected idxd-dependent systems are business-critical. There is no source evidence of active exploitation, but kernel null dereferences can affect availability, so confirm exposure and patch status during the next maintenance cycle.

Technical view

The issue is in dmaengine idxd handling around idxd_cmd_exec. Some callers pass a null status pointer, while a later change assigned through status before the existing null check. The fix adds a null check before assignment. Sources describe this as a Coverity-detected explicit null dereference.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions or downstream builds that include the vulnerable idxd driver code. The bundle lists Linux 5.10.38, 5.11, 5.11.22, 5.12.5, and 5.13 as affected indicators, but downstream distro status must be verified.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not claim active exploitation or provide a public exploit. The evidence describes a potential null dereference, not remote code execution. Trigger conditions beyond affected idxd_cmd_exec call paths are not documented in the bundle.

Researcher notes

Evidence is limited to the CVE record and kernel stable references. The root cause is a missing status null check introduced after callers already relied on null being allowed. Avoid assuming exploitability, privilege requirements, or impact beyond potential null dereference without additional vendor analysis.

Mitigation direction

  • Apply vendor kernel updates containing the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported patches and package-specific status.
  • Prioritize hosts that use the idxd dmaengine driver or related accelerator hardware.
  • Track the CVE until severity and downstream advisories are complete.

Validation and detection

  • Inventory running kernel versions across Linux fleets.
  • Compare kernel builds against the referenced stable fix commits or distro advisories.
  • Confirm whether the idxd driver is built, loaded, or operationally required.
  • Review vulnerability scanner findings for distro-specific false positives or backports.
Prepared
Confidence
medium
Sources
6

Public sources used

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-47003 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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux40e3b5c128645d2ddad12310c7be98758cafb2b0, 89e3becd8f821e507052e012d2559dcda59f538e, 89e3becd8f821e507052e012d2559dcda59f538e, 89e3becd8f821e507052e012d2559dcda59f538eunaffected
LinuxLinux5.11, 0, 5.10.38, 5.11.22, 5.12.5, 5.13affected
Weakness

CWE details

No CWE listed

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