CVE-2022-50024: dmaengine: dw-axi-dmac: do not print NULL LLI during error
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: dw-axi-dmac: do not print NULL LLI during error
During debugging we have seen an issue where axi_chan_dump_lli()
is passed a NULL LLI pointer which ends up causing an OOPS due
to trying to get fields from it. Simply print NULL LLI and exit
to avoid this.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50024 is a Linux kernel bug in the DesignWare AXI DMA controller driver. Under an error/debug condition, the kernel could dereference a NULL pointer and OOPS, causing local instability or denial of service. No public source in the bundle indicates active exploitation or a remote attack path.
Executive priority
Treat as a targeted reliability risk, not a broadly confirmed internet-facing emergency. Patch through normal kernel maintenance, prioritizing embedded, appliance, or SoC-based systems using this DMA controller. Escalate if the driver is present on business-critical systems where kernel crashes affect availability.
Technical view
The dw-axi-dmac dmaengine driver’s axi_chan_dump_lli() could receive a NULL LLI pointer and then read fields from it, triggering a kernel OOPS. The fix changes the error path to print that the LLI is NULL and return. CVSS and CWE data are not provided in the source bundle.
Likely exposure
Exposure is likely limited to Linux systems using the dw-axi-dmac driver, typically hardware with Synopsys DesignWare AXI DMA. Generic Linux servers may not be affected if this driver is absent or unused. The source bundle lists affected Linux kernel ranges and stable fixes, but does not describe distribution-specific package status.
Exploitation context
The available sources describe a crash/OOPS during debugging or error handling, not privilege escalation or code execution. There is no KEV listing and no cited source claiming active exploitation. Practical risk depends on whether an attacker can trigger the driver error path on affected hardware.
Researcher notes
The vulnerable behavior is a NULL pointer dereference in axi_chan_dump_lli() when passed a NULL LLI. The public record names upstream stable commits but provides no CVSS, CWE, exploit details, or confirmed attack scenario. Distribution backports may use different version numbers, so patch presence matters more than upstream version alone.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
If updating is delayed, check vendor guidance for platform-specific mitigations.
Prioritize systems where dw-axi-dmac hardware and driver are present.
Track Linux distribution advisories for backported fixes.
Validation and detection
Inventory Linux kernel versions against vendor advisory status.
Confirm whether the dw-axi-dmac driver is built, loaded, or used.
Verify the referenced upstream stable commit is present or backported.
Review kernel logs for related DMA controller OOPS events.
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-50024 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
4Source 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.
Jun 18, 2025, 11:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.