LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50079: drm/amd/display: Check correct bounds for stream encoder instances for DCN303

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check correct bounds for stream encoder instances for DCN303 [Why & How] eng_id for DCN303 cannot be more than 1, since we have only two instances of stream encoders. Check the correct boundary condition for engine ID for DCN303 prevent the potential out of bounds access.

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-50079 is a Linux kernel AMD display driver issue. The vulnerable code could check the wrong limit for DCN303 stream encoder IDs, creating potential out-of-bounds access. The public bundle does not provide CVSS, CWE, confirmed impact, or exploitation evidence.

Executive priority

Treat this as a normal kernel maintenance item unless your environment has broad AMD display exposure on affected kernels. There is no supplied evidence of active exploitation, but kernel memory-safety issues should not remain untracked.

Technical view

In drm/amd/display, DCN303 has only two stream encoder instances, so engine IDs should not exceed 1. The resolved issue corrects the boundary condition for that engine ID to prevent potential out-of-bounds access. Source data identifies Linux kernel versions and stable commits, but not a complete exploitability assessment.

Likely exposure

Exposure is most relevant to Linux systems using the AMD display driver path that includes DCN303 code and kernels identified as affected in the source bundle. Headless systems or systems without this driver path may be less likely exposed, but asset validation is required.

Exploitation context

The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation or public exploit use. It describes a potential out-of-bounds access condition only; practical attack prerequisites and impact are not established in the provided sources.

Researcher notes

The available record lacks CVSS, CWE, and detailed attack context. Analysis should focus on the referenced kernel commits, the DCN303 stream encoder bounds logic, and distribution-specific backport mapping before making stronger risk claims.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes or distribution backports.
  • Check Linux distribution advisories for exact fixed package versions.
  • Prioritize systems using AMD display/DCN303 code paths for validation and patching.
  • If patching is delayed, follow vendor guidance for supported temporary mitigations.

Validation and detection

  • Inventory affected Linux kernel versions listed in the source bundle.
  • Confirm whether hosts load or include the AMD display driver path.
  • Compare kernel source or package changelog against the referenced stable commits.
  • Verify distribution backport status before marking a host remediated.
Prepared
Confidence
medium
Sources
5

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-50079 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
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcd6d421e3d1ad5926b74091254e345db730e7706, cd6d421e3d1ad5926b74091254e345db730e7706, cd6d421e3d1ad5926b74091254e345db730e7706unaffected
LinuxLinux5.14, 0, 5.15.63, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.