# crypto: qat - fix DMA transfer direction

CVE record · `CVE-2022-50774`

- **Identifiers:** `CVE-2022-50774`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Dec 2025, 13:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `d370cec3219490656d72f5ae6e5df32c113c5a44 to before 426d5bc089e7731e36b514d1beca19e777a2d653` (git)
  - affected: `d370cec3219490656d72f5ae6e5df32c113c5a44 to before 1f1ab76e251521bd2fa5244473efcf663792745d` (git)
  - affected: `d370cec3219490656d72f5ae6e5df32c113c5a44 to before 429348d4f675e9eb418d0829064c4d7d06bd66a3` (git)
  - affected: `d370cec3219490656d72f5ae6e5df32c113c5a44 to before c4c9d9edf4848aed89516b23b88950b194beff6a` (git)
  - affected: `d370cec3219490656d72f5ae6e5df32c113c5a44 to before cf5bb835b7c8a5fee7f26455099cca7feb57f5e9` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.17`
  - unaffected: `before 3.17` (semver)
  - unaffected: `5.10.150 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.75 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.17 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0.3 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 17th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Dec 2025, 13:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50774)

## Sources

- [CVE List: CVE-2022-50774](https://www.cve.org/CVERecord?id=CVE-2022-50774)
- [NVD: CVE-2022-50774](https://nvd.nist.gov/vuln/detail/CVE-2022-50774)

### References from the CNA

- <https://git.kernel.org/stable/c/426d5bc089e7731e36b514d1beca19e777a2d653>
- <https://git.kernel.org/stable/c/1f1ab76e251521bd2fa5244473efcf663792745d>
- <https://git.kernel.org/stable/c/429348d4f675e9eb418d0829064c4d7d06bd66a3>
- <https://git.kernel.org/stable/c/c4c9d9edf4848aed89516b23b88950b194beff6a>
- <https://git.kernel.org/stable/c/cf5bb835b7c8a5fee7f26455099cca7feb57f5e9>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50774>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50774/>. Everything for agents: <https://agentprime.io/llms.txt>.
