Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Fixed version: Linux Linux 1f1ab76e251521bd2fa5244473efcf663792745d, 426d5bc089e7731e36b514d1beca19e777a2d653, 429348d4f675e9eb418d0829064c4d7d06bd66a3.

Low priority for now. Upgrade to Linux Linux 1f1ab76e251521bd2fa5244473efcf663792745d, 426d5bc089e7731e36b514d1beca19e777a2d653, 429348d4f675e9eb418d0829064c4d7d06bd66a3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50774

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.17affected
    • d370cec3219490656d72f5ae6e5df32c113c5a44 and later · before 426d5bc089e7731e36b514d1beca19e777a2d653affected · git
    • d370cec3219490656d72f5ae6e5df32c113c5a44 and later · before 1f1ab76e251521bd2fa5244473efcf663792745daffected · git
    • d370cec3219490656d72f5ae6e5df32c113c5a44 and later · before 429348d4f675e9eb418d0829064c4d7d06bd66a3affected · git
    • d370cec3219490656d72f5ae6e5df32c113c5a44 and later · before c4c9d9edf4848aed89516b23b88950b194beff6aaffected · git
    • d370cec3219490656d72f5ae6e5df32c113c5a44 and later · before cf5bb835b7c8a5fee7f26455099cca7feb57f5e9affected · git
    • before 3.17not affected · semver
    • 5.10.150 and later · up to and including 5.10.*not affected · semver
    • 5.15.75 and later · up to and including 5.15.*not affected · semver
    • 5.19.17 and later · up to and including 5.19.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.3-16.0.3-1
Red Hat:rhel_eus:9.0::appstreambpftool-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debug-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debug-develbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-develbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-devel-matchedbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-docbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-tools-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-zfcpdump-develbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamperfbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamperf-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreampython3-perf-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseosbpftoolbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseoskernelbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseoskernel-abi-stablelistsbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseoskernel-corebefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0

+14

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50772Dec 24, 2025 · netdevsim: fix memory leak in nsim_bus_dev_new()
    0Monitor
  • ← EarlierCVE-2022-50773Dec 24, 2025 · ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt
    0Monitor
  • Later →CVE-2022-50775Dec 24, 2025 · RDMA/hns: Fix refcount leak in hns_roce_mmap
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1f1ab76e251521bd2fa5244473efcf663792745dVendor (CNA)
Linux Linux426d5bc089e7731e36b514d1beca19e777a2d653Vendor (CNA)
Linux Linux429348d4f675e9eb418d0829064c4d7d06bd66a3Vendor (CNA)
Linux Linuxc4c9d9edf4848aed89516b23b88950b194beff6aVendor (CNA)
Linux Linuxcf5bb835b7c8a5fee7f26455099cca7feb57f5e9Vendor (CNA)
debian:linux6.0.3-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-x86_640:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-devel0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-devel-matched0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-doc0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records