LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49969: drm/amd/display: clear optc underflow before turn off odm clock

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: clear optc underflow before turn off odm clock [Why] After ODM clock off, optc underflow bit will be kept there always and clear not work. We need to clear that before clock off. [How] Clear that if have when clock off.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns a Linux kernel AMD display driver bug where a display underflow status bit can remain stuck after a display clock is turned off. The public record does not state a security impact, CVSS score, CWE, or active exploitation. Treat urgency as exposure-management rather than emergency response unless your vendor assigns higher severity.

Executive priority

Set this to normal patch-cycle priority unless your Linux vendor rates it higher. There is no cited evidence of active exploitation or severe impact, but kernel driver fixes should still be tracked because fleet exposure can be broad and branch-specific.

Technical view

The issue is in drm/amd/display. The source description says the OPTC underflow bit cannot be cleared after the ODM clock is disabled, so the fix clears the bit before clock-off. Affected Linux versions are listed, with multiple stable kernel commit references. No exploit mechanics or attacker prerequisites are provided.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the AMD display stack. The source lists Linux versions 4.15, 4.19.257, 5.4.212, 5.10.141, 5.15.65, 5.19.7, and 6.0 as affected, but branch-specific interpretation should come from distro advisories.

Exploitation context

The provided sources do not show active exploitation, public weaponization, KEV listing, or a practical attack scenario. The evidence describes a kernel display-driver correctness fix. Security impact is not explained in the bundle, so exploitation risk cannot be confidently assessed from these sources alone.

Researcher notes

Evidence is incomplete: no CVSS, CWE, exploit status, or detailed impact is included. The strongest technical signal is the upstream stable fix description. Avoid assuming privilege escalation, denial of service, or confidentiality impact without additional vendor analysis.

Mitigation direction

  • Apply Linux distribution kernel updates that include the referenced stable commits.
  • Review vendor or distro advisories for branch-specific fixed package versions.
  • Prioritize systems with AMD GPUs and active display workloads for inventory review.
  • Do not deploy affected kernel branches where fixed updates are available.
  • Track the CVE record for later CVSS, CWE, or impact updates.

Validation and detection

  • Inventory Linux kernel versions against the affected version list in the CVE record.
  • Check kernel package changelogs for the referenced stable commit identifiers.
  • Confirm AMD display driver exposure where kernel inventory shows affected versions.
  • Verify vulnerability scanners recognize the installed kernel as fixed after update.
  • Document any systems awaiting vendor guidance or maintenance windows.
Prepared
Confidence
medium
Sources
8

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-49969 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
7Source 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
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7cunaffected
LinuxLinux4.15, 0, 4.19.257, 5.4.212, 5.10.141, 5.15.65, 5.19.7, 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.