# CVE-2026-98886: drm/gma500: return errors from Oaktrail HDMI I2C reads


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110623, BELL-CVE-2026-98886, DEBIAN-CVE-2026-98886, GHSA-mmv9-fq67-57xh, UBUNTU-CVE-2026-98886

## What is CVE-2026-98886?

CVE-2026-98886 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/gma500: return errors from Oaktrail HDMI I2C reads

xfer_read() waits for the HDMI I2C transaction to reach
I2C_TRANSACTION_DONE, but it ignores both timeout and signal returns from
wait_for_completion_interruptible_timeout().  If the interrupt never
advances the transaction state, the loop can wait forever.

Return -ETIMEDOUT when the completion wait expires, propagate interrupted
waits, and make the I2C master_xfer callback return the first transfer
error instead of reporting a successful message count.

## Which versions are affected by CVE-2026-98886?


## How do I fix CVE-2026-98886?

Upgrade to a fixed version.

## Is CVE-2026-98886 being exploited?

There is no known exploitation of CVE-2026-98886 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98886 and fix it if it is affected.

What it is: CVE-2026-98886 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98886 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98886/ (Markdown: https://insights.sbomify.com/CVE-2026-98886/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98886
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98886
- OSV: https://osv.dev/vulnerability/CVE-2026-98886

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98886/
Summaries are generated and may contain mistakes; the official description above is the record.