# CVE-2026-74380: gpu: host1x: Fix iommu_map_sgtable() return value check

> An integer overflow in the Linux kernel host1x driver can cause incorrect error handling, potentially leading to a denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74380, DEBIAN-CVE-2026-74380, GHSA-jqc5-8mvc-pp3w, UBUNTU-CVE-2026-74380

## What is CVE-2026-74380?

CVE-2026-74380 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

gpu: host1x: Fix iommu_map_sgtable() return value check

Commit "iommu: return full error code from iommu_map_sg[_atomic]()"
changed iommu_map_sgtable() to return an ssize_t and negative values
in error cases, rather than a size_t and a zero.

pin_job() also was incorrectly assigning to 'int', which could cause
overflows into negative values.

Update pin_job() to correctly check for errors from iommu_map_sgtable.

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


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

Apply the vendor's patch.

## Is CVE-2026-74380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74380 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74380 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-74380/ (Markdown: https://insights.sbomify.com/CVE-2026-74380/index.md)
```

## Sources

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

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