LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50362: dmaengine: hisilicon: Add multi-thread support for a DMA channel

In the Linux kernel, the following vulnerability has been resolved: dmaengine: hisilicon: Add multi-thread support for a DMA channel When we get a DMA channel and try to use it in multiple threads it will cause oops and hanging the system. % echo 100 > /sys/module/dmatest/parameters/threads_per_chan % echo 100 > /sys/module/dmatest/parameters/iterations % echo 1 > /sys/module/dmatest/parameters/run [383493.327077] Unable to handle kernel paging request at virtual address dead000000000108 [383493.335103] Mem abort info: [383493.335103] ESR = 0x96000044 [383493.335105] EC = 0x25: DABT (current EL), IL = 32 bits [383493.335107] SET = 0, FnV = 0 [383493.335108] EA = 0, S1PTW = 0 [383493.335109] FSC = 0x04: level 0 translation fault [383493.335110] Data abort info: [383493.335111] ISV = 0, ISS = 0x00000044 [383493.364739] CM = 0, WnR = 1 [383493.367793] [dead000000000108] address between user and kernel address ranges [383493.375021] Internal error: Oops: 96000044 [#1] PREEMPT SMP [383493.437574] CPU: 63 PID: 27895 Comm: dma0chan0-copy2 Kdump: loaded Tainted: GO 5.17.0-rc4+ #2 [383493.457851] pstate: 204000c9 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [383493.465331] pc : vchan_tx_submit+0x64/0xa0 [383493.469957] lr : vchan_tx_submit+0x34/0xa0 This occurs because the transmission timed out, and that's due to data race. Each thread rewrite channels's descriptor as soon as device_issue_pending is called. It leads to the situation that the driver thinks that it uses the right descriptor in interrupt handler while channels's descriptor has been changed by other thread. The descriptor which in fact reported interrupt will not be handled any more, as well as its tx->callback. That's why timeout reports. With current fixes channels' descriptor changes it's value only when it has been used. A new descriptor is acquired from vc->desc_issued queue that is already filled with descriptors that are ready to be sent. Threads have no direct access to DMA channel descriptor. In case of channel's descriptor is busy, try to submit to HW again when a descriptor is completed. In this case, vc->desc_issued may be empty when hisi_dma_start_transfer is called, so delete error reporting on this. Now it is just possible to queue a descriptor for further processing.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50362 is a Linux kernel flaw in the Hisilicon DMA engine driver. When one DMA channel is used concurrently by multiple threads, a race condition can trigger a kernel oops or hang, causing system unavailability. It requires local access with privileges and is not listed as actively exploited in KEV.

Executive priority

Treat as a targeted availability risk, not an internet-scale emergency. Prioritize patching for systems using Hisilicon DMA hardware, shared compute environments, and platforms where local users can run workloads. Routine kernel update cycles may be acceptable if exposure is low and compensating controls exist.

Technical view

The issue is a data race around a DMA channel descriptor in the Hisilicon dmaengine driver. Concurrent submissions can overwrite the channel descriptor after device_issue_pending, causing interrupt handling and callbacks to reference the wrong descriptor. The reported impact is kernel oops/hang, with CVSS 5.5: local, low complexity, low privileges, availability high.

Likely exposure

Exposure is most relevant to Linux systems using affected kernel versions with Hisilicon DMA hardware and driver functionality enabled. The source lists Linux as affected across versions including 5.6, 5.10.150, 5.15.75, 5.19.17, 6.0.3, and 6.1, but version-range detail is incomplete.

Exploitation context

The source describes triggering through local multi-threaded use of a DMA channel, not remote network access. Exploitation would be aimed at denial of service rather than data theft or code execution. No source provided here reports active exploitation or inclusion in CISA KEV.

Researcher notes

The public record provides a kernel commit-level explanation and stable fix references, but not a complete affected-version matrix by distribution. Analysis should focus on whether downstream kernels include the descriptor-handling change. Avoid assuming exploitability on systems without the relevant Hisilicon DMA driver path.

Mitigation direction

  • Identify Linux hosts using Hisilicon DMA engine support and affected kernel versions.
  • Review distribution or kernel vendor advisories for CVE-2022-50362 applicability.
  • Update to a kernel build containing the referenced stable fixes where applicable.
  • Prioritize systems where local users or workloads can exercise DMA testing or driver paths.

Validation and detection

  • Inventory running kernel versions and compare against vendor guidance for this CVE.
  • Confirm whether Hisilicon dmaengine driver support is present and in use.
  • Check vendor kernel changelogs for the referenced stable commit IDs.
  • Monitor affected systems for kernel oops, DMA timeout, or unexplained hangs.
Prepared
Confidence
medium
Sources
7

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-50362 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-50362Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe9f08b65250d73ab70e79e194813f52b8d306784, e9f08b65250d73ab70e79e194813f52b8d306784, e9f08b65250d73ab70e79e194813f52b8d306784, e9f08b65250d73ab70e79e194813f52b8d306784, e9f08b65250d73ab70e79e194813f52b8d306784unaffected
LinuxLinux5.6, 0, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

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