Service crash via oversized MTP read response
Published Sep 1, 2026 · Updated Sep 2, 2026
Out-of-bounds read in GVfs before 1.60.2 allows physically proximate attackers to crash gvfsd-mtp through a malicious MTP device. do_read() in gvfsbackendmtp.c passes the device-reported length to memcpy() without limiting it to the client's requested size. Exploitation requires physical device connection and a file read from the mounted device; the resulting segmentation fault interrupts that MTP session.
Summary
What happened
Out-of-bounds read in GVfs before 1.60.2 allows physically proximate attackers to crash gvfsd-mtp through a malicious MTP device. do_read() in gvfsbackendmtp.c passes the device-reported length to memcpy() without limiting it to the client's requested size. Exploitation requires physical device connection and a file read from the mounted device; the resulting segmentation fault interrupts that MTP session.
The record
- CVE
- CVE-2026-84270
- Published
- Sep 1, 2026
- Updated
- Sep 2, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-125, T1499.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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