Red Hat Enterprise Linux MTP backend gvfsbackendmtp.c do_read memory corruption

Summaryinfo

A vulnerability classified as problematic has been found in Red Hat Enterprise Linux. This impacts the function do_read of the file gvfsbackendmtp.c of the component MTP backend. Performing a manipulation results in memory corruption. This vulnerability is known as CVE-2026-84270. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability was found in Red Hat Enterprise Linux (version now known). It has been classified as problematic. This affects the function do_read of the file gvfsbackendmtp.c of the component MTP backend. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on availability. The summary by CVE is:

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.

The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-84270 since 09/01/2026. The exploitability is told to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/01/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Operating System

Vendor

• Red Hat

Name

• Enterprise Linux

License

• commercial

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion