LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50774: crypto: qat - fix DMA transfer direction

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix DMA transfer direction When CONFIG_DMA_API_DEBUG is selected, while running the crypto self test on the QAT crypto algorithms, the function add_dma_entry() reports a warning similar to the one below, saying that overlapping mappings are not supported. This occurs in tests where the input and the output scatter list point to the same buffers (i.e. two different scatter lists which point to the same chunks of memory). The logic that implements the mapping uses the flag DMA_BIDIRECTIONAL for both the input and the output scatter lists which leads to overlapped write mappings. These are not supported by the DMA layer. Fix by specifying the correct DMA transfer directions when mapping buffers. For in-place operations where the input scatter list matches the output scatter list, buffers are mapped once with DMA_BIDIRECTIONAL, otherwise input buffers are mapped using the flag DMA_TO_DEVICE and output buffers are mapped with DMA_FROM_DEVICE. Overlapping a read mapping with a write mapping is a valid case in dma-coherent devices like QAT. The function that frees and unmaps the buffers, qat_alg_free_bufl() has been changed accordingly to the changes to the mapping function. DMA-API: 4xxx 0000:06:00.0: cacheline tracking EEXIST, overlapping mappings aren't supported WARNING: CPU: 53 PID: 4362 at kernel/dma/debug.c:570 add_dma_entry+0x1e9/0x270 ... Call Trace: dma_map_page_attrs+0x82/0x2d0 ? preempt_count_add+0x6a/0xa0 qat_alg_sgl_to_bufl+0x45b/0x990 [intel_qat] qat_alg_aead_dec+0x71/0x250 [intel_qat] crypto_aead_decrypt+0x3d/0x70 test_aead_vec_cfg+0x649/0x810 ? number+0x310/0x3a0 ? vsnprintf+0x2a3/0x550 ? scnprintf+0x42/0x70 ? valid_sg_divisions.constprop.0+0x86/0xa0 ? test_aead_vec+0xdf/0x120 test_aead_vec+0xdf/0x120 alg_test_aead+0x185/0x400 alg_test+0x3d8/0x500 ? crypto_acomp_scomp_free_ctx+0x30/0x30 ? __schedule+0x32a/0x12a0 ? ttwu_queue_wakelist+0xbf/0x110 ? _raw_spin_unlock_irqrestore+0x23/0x40 ? try_to_wake_up+0x83/0x570 ? _raw_spin_unlock_irqrestore+0x23/0x40 ? __set_cpus_allowed_ptr_locked+0xea/0x1b0 ? crypto_acomp_scomp_free_ctx+0x30/0x30 cryptomgr_test+0x27/0x50 kthread+0xe6/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50774 is a Linux kernel issue in the Intel QAT crypto driver’s DMA buffer handling. The described impact is a DMA-API warning during crypto self-tests when input and output buffers overlap. Business urgency appears limited to systems using QAT, but severity is not published in the source data.

Executive priority

Treat as targeted kernel hygiene for QAT-enabled Linux systems, not an enterprise-wide emergency based on current sources. Patch through normal kernel maintenance unless your environment depends heavily on Intel QAT acceleration.

Technical view

The QAT crypto code mapped both input and output scatter lists with DMA_BIDIRECTIONAL, creating unsupported overlapping write mappings. The fix maps in-place operations once as bidirectional, otherwise input as DMA_TO_DEVICE and output as DMA_FROM_DEVICE, with matching unmap changes in qat_alg_free_bufl().

Likely exposure

Exposure is most relevant to Linux systems using Intel QAT crypto acceleration and affected kernel code paths. Systems without QAT hardware or the intel_qat driver are less likely to be exposed based on the provided description.

Exploitation context

The provided sources do not show active exploitation, KEV listing, public exploit details, or a CVSS score. The observed behavior is a kernel DMA debugging warning during crypto self-testing, so real-world security impact is unclear from available evidence.

Researcher notes

The record lacks CVSS, CWE, and explicit impact beyond DMA-API debug warnings. Affected version data appears broad and commit-based. Focus analysis on QAT AEAD in-place buffer handling and stable backport coverage rather than assuming exploitability.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable QAT DMA direction fixes.
  • Check your Linux distribution’s advisory for backported fixes and supported kernel packages.
  • Prioritize systems using Intel QAT crypto acceleration.
  • If updates are unavailable, consult vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory hosts with Intel QAT hardware or the intel_qat kernel driver loaded.
  • Compare installed kernel packages against vendor advisories and referenced stable commits.
  • Review kernel logs for DMA-API overlapping mapping warnings involving intel_qat.
  • Confirm patched kernels pass relevant crypto self-tests without the reported warning.
Prepared
Confidence
medium
Sources
7

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-2022-50774 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
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd370cec3219490656d72f5ae6e5df32c113c5a44, d370cec3219490656d72f5ae6e5df32c113c5a44, d370cec3219490656d72f5ae6e5df32c113c5a44, d370cec3219490656d72f5ae6e5df32c113c5a44, d370cec3219490656d72f5ae6e5df32c113c5a44unaffected
LinuxLinux3.17, 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.