{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50774 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50774 is a vulnerability in Linux, published on 24 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50774 and fix it if it is affected.\n\nWhat it is: CVE-2022-50774 is a vulnerability in Linux, published on 24 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50774 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50774/ (Markdown: https://insights.sbomify.com/CVE-2022-50774/index.md)","id":"CVE-2022-50774","markdown":"https://insights.sbomify.com/CVE-2022-50774/index.md","name":"CVE-2022-50774","record":{"aliases":["DEBIAN-CVE-2022-50774","GHSA-c9vq-m3c3-2m7g","UBUNTU-CVE-2022-50774"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A bug in the Intel QAT crypto driver causes DMA mapping warnings and potential instability when CONFIG_DMA_API_DEBUG is enabled during self-tests.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - fix DMA transfer direction\n\nWhen CONFIG_DMA_API_DEBUG is selected, while running the crypto self\ntest on the QAT crypto algorithms, the function add_dma_entry() reports\na warning similar to the one below, saying that overlapping mappings\nare not supported. This occurs in tests where the input and the output\nscatter list point to the same buffers (i.e. two different scatter lists\nwhich point to the same chunks of memory).\n\nThe logic that implements the mapping uses the flag DMA_BIDIRECTIONAL\nfor both the input and the output scatter lists which leads to\noverlapped write mappings. These are not supported by the DMA layer.\n\nFix by specifying the correct DMA transfer directions when mapping\nbuffers. For in-place operations where the input scatter list\nmatches the output scatter list, buffers are mapped once with\nDMA_BIDIRECTIONAL, otherwise input buffers are mapped using the flag\nDMA_TO_DEVICE and output buffers are mapped with DMA_FROM_DEVICE.\nOverlapping a read mapping with a write mapping is a valid case in\ndma-coherent devices like QAT.\nThe function that frees and unmaps the buffers, qat_alg_free_bufl()\nhas been changed accordingly to the changes to the mapping function.\n\n   DMA-API: 4xxx 0000:06:00.0: cacheline tracking EEXIST, overlapping mappings aren't supported\n   WARNING: CPU: 53 PID: 4362 at kernel/dma/debug.c:570 add_dma_entry+0x1e9/0x270\n   ...\n   Call Trace:\n   dma_map_page_attrs+0x82/0x2d0\n   ? preempt_count_add+0x6a/0xa0\n   qat_alg_sgl_to_bufl+0x45b/0x990 [intel_qat]\n   qat_alg_aead_dec+0x71/0x250 [intel_qat]\n   crypto_aead_decrypt+0x3d/0x70\n   test_aead_vec_cfg+0x649/0x810\n   ? number+0x310/0x3a0\n   ? vsnprintf+0x2a3/0x550\n   ? scnprintf+0x42/0x70\n   ? valid_sg_divisions.constprop.0+0x86/0xa0\n   ? test_aead_vec+0xdf/0x120\n   test_aead_vec+0xdf/0x120\n   alg_test_aead+0x185/0x400\n   alg_test+0x3d8/0x500\n   ? crypto_acomp_scomp_free_ctx+0x30/0x30\n   ? __schedule+0x32a/0x12a0\n   ? ttwu_queue_wakelist+0xbf/0x110\n   ? _raw_spin_unlock_irqrestore+0x23/0x40\n   ? try_to_wake_up+0x83/0x570\n   ? _raw_spin_unlock_irqrestore+0x23/0x40\n   ? __set_cpus_allowed_ptr_locked+0xea/0x1b0\n   ? crypto_acomp_scomp_free_ctx+0x30/0x30\n   cryptomgr_test+0x27/0x50\n   kthread+0xe6/0x110\n   ? kthread_complete_and_exit+0x20/0x20\n   ret_from_fork+0x1f/0x30","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"crypto: qat - fix DMA transfer direction","id":"CVE-2022-50774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"RDMA/hns: Fix refcount leak in hns_roce_mmap","id":"CVE-2022-50775"},"packages":[],"prev":{"headline":"ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt","id":"CVE-2022-50773"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A bug in the Intel QAT crypto driver causes DMA mapping warnings and potential instability when CONFIG_DMA_API_DEBUG is enabled during self-tests.","url":"https://insights.sbomify.com/CVE-2022-50774/"}