USB Request Structure DMA Coherency Bypass in Linux Kernel

Publication date: 2026-05-27

Last updated on: 2026-06-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: media: rc: igorplugusb: heed coherency rules In a control request, the USB request structure can be subject to DMA on some HCs. Hence it must obey the rules for DMA coherency. Allocate it separately.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-25

Generated

2026-07-06

AI Q&A

2026-05-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-46091

EUVD

EUVD-2026-32474

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.7 (inc) to 6.12.86 (exc)
linux	linux_kernel	From 6.2 (inc) to 6.6.140 (exc)
linux	linux_kernel	From 6.13 (inc) to 6.18.27 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.4 (exc)
linux	linux_kernel	From 5.16 (inc) to 6.1.176 (exc)
linux	linux_kernel	From 5.11 (inc) to 5.15.210 (exc)
linux	linux_kernel	From 3.19 (inc) to 5.10.259 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's media subsystem, specifically in the igorplugusb driver. It involves the handling of USB control requests where the USB request structure can be subject to Direct Memory Access (DMA) on some Host Controllers (HCs). The issue arises because the request structure does not properly follow DMA coherency rules, which are necessary to ensure data integrity during DMA operations. The fix involves allocating the USB request structure separately to maintain proper DMA coherency.

Impact Analysis

Improper handling of DMA coherency in USB request structures can lead to data corruption or unexpected behavior in the affected media driver. This could potentially cause system instability, crashes, or incorrect processing of USB control requests. However, specific impacts such as privilege escalation or remote code execution are not detailed in the provided information.

Hi! I’m here to help you understand CVE-2026-46091. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70