Read hang via ignored HDMI I2C timeouts
Published Oct 23, 2026 · Updated Oct 23, 2026
Linux gma500 HDMI I2C read handling allows attackers to hang a read operation when a transaction never reaches completion. The xfer_read() function ignores timeout and signal results from wait_for_completion_interruptible_timeout(), repeatedly waiting instead of returning an error. The path requires Oak Trail HDMI hardware and the gma500 driver; public sources do not establish attacker control over the missing completion interrupt or a system-wide hang.
Summary
What happened
Linux gma500 HDMI I2C read handling allows attackers to hang a read operation when a transaction never reaches completion. The xfer_read() function ignores timeout and signal results from wait_for_completion_interruptible_timeout(), repeatedly waiting instead of returning an error. The path requires Oak Trail HDMI hardware and the gma500 driver; public sources do not establish attacker control over the missing completion interrupt or a system-wide hang.
The record
- CVE
- CVE-2026-98886
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=0 <5.10.271
- Affected versionversion=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <09a950950e7e4e74e021e60941c8e816ef1b4f71
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <15c6d7f7127a53b7312232178ecf03e5850161d2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <898d209157fe2a245f7d9fe28c5921037d8b5033
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8add43887cca1fe11a0ded62199ce726901d3f20
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9b5ce5c496efd20c1c662cedba88465d39ec1f93
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c268df0653ab07bafc3d191e74ea097e3d9b9e69
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f85e8224bd4e1a0939cbfe13a6220fbddf61127c
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us