# CVE-2026-84270: Gvfs: mtp: out-of-bounds read in do_read()

> A malicious MTP device can trigger an out-of-bounds read in gvfs, causing a segmentation fault and denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-84270, GHSA-2rh6-86rx-p849, UBUNTU-CVE-2026-84270

## What is CVE-2026-84270?

CVE-2026-84270 is a medium-severity memory corruption vulnerability in GNOME Red Hat Enterprise Linux 10, published on 1 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the MTP backend in gvfs. When reading a file from a mounted MTP device, do_read() in gvfsbackendmtp.c trusts the data length returned by the device without limiting it to the original size requested by the client. If a malicious MTP device responds with more bytes than requested, this unrestricted length is passed directly to memcpy(). This causes the operation to read memory outside the intended boundaries. This allows an attacker who plugs in a malicious MTP device to cause a segmentation fault when a file is read and crash the gvfsd-mtp process, resulting in a denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-84270 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84270 is a medium-severity memory corruption vulnerability in GNOME Red Hat Enterprise Linux 10, published on 1 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-84270 in the wild and no public exploit code.

Affected product: GNOME Red Hat Enterprise Linux 10. 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-84270/ (Markdown: https://insights.sbomify.com/CVE-2026-84270/index.md)
```

## Sources

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

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