# drm/amd/display: Fix optc2_configure warning on dcn314

CVE record · `CVE-2022-49773`

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

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:09 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: `2ce0b2186c057a54a4d980b296bd1659d0091716 to before f67ef5aa88e3db0a13ae3befab2ddf14ac00a91c` (git)
  - affected: `2ce0b2186c057a54a4d980b296bd1659d0091716 to before e7e4f77c991c9abf90924929a9d55f90b0bb78de` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.0`
  - unaffected: `before 6.0` (semver)
  - unaffected: `6.0.10 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> This Linux kernel fix addresses the amdgpu display driver on the dcn314 hardware, where a CRC configuration path wrongly set registers that do not apply to that hardware and triggered a kernel warning. The source gives few details on the attack surface or impact beyond the warning. A fix is available in the listed kernel versions, so upgrade to a kernel version that includes the fix (6.0.10 or later in the 6.0 series, or 6.1 and later).

Written 16 Nov 2026.

## 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.0017, the 6th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 14:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49773)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49773)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/f67ef5aa88e3db0a13ae3befab2ddf14ac00a91c>
- <https://git.kernel.org/stable/c/e7e4f77c991c9abf90924929a9d55f90b0bb78de>

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-49773>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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