Persistent underflow status via late clearing
Published Jun 18, 2025 · Updated Aug 15, 2026
Display pipeline state-handling error in affected Linux kernels leaves OPTC underflow status uncleared after ODM clock-off. The dcn10_optc.c clock-off path turns off the ODM clock before clearing an existing OPTC underflow bit, after which the hardware keeps the bit set and later clearing fails. Reachability depends on an AMD display-pipeline underflow timing event that userspace cannot directly invoke or reliably influence; published sources report only persistent stale underflow status.
Summary
What happened
Display pipeline state-handling error in affected Linux kernels leaves OPTC underflow status uncleared after ODM clock-off. The dcn10_optc.c clock-off path turns off the ODM clock before clearing an existing OPTC underflow bit, after which the hardware keeps the bit set and later clearing fails. Reachability depends on an AMD display-pipeline underflow timing event that userspace cannot directly invoke or reliably influence; published sources report only persistent stale underflow status.
The record
- CVE
- CVE-2022-49969
- Published
- Jun 18, 2025
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.15
- Affected versionversion=70ccab604049bbb995a57ab3b7fe8a3c2fdbb736 <3101839b080137c367f3f88c2a040f791de880aa
- Affected versionversion=70ccab604049bbb995a57ab3b7fe8a3c2fdbb736 <3c1dfeaeb3b4e3ea656041da1241e6ee3c3b3202
- Affected versionversion=70ccab604049bbb995a57ab3b7fe8a3c2fdbb736 <443687798d6f094412b7312b64b3bb4d99aedff7
- Affected versionversion=70ccab604049bbb995a57ab3b7fe8a3c2fdbb736 <5ee30bcfdb32526233d2572f3d9ec371928679f1
- Affected versionversion=70ccab604049bbb995a57ab3b7fe8a3c2fdbb736 <814b756d4ec3a8728debb116cf49005feada7750
- Affected versionversion=70ccab604049bbb995a57ab3b7fe8a3c2fdbb736 <b2a93490201300a749ad261b5c5d05cb50179c44
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo