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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver flaw in the igorplugusb remote-control USB driver. The published description says a USB control-request structure may be touched by DMA on some host controllers and was not allocated according to DMA coherency rules. Business risk is unclear because no CVSS, impact detail, or exploitation evidence is provided.
Executive priority
Treat as a tracked kernel maintenance item, not an emergency, unless your environment uses the affected driver or a vendor raises severity. The current public record lacks impact scoring and exploitation evidence, so urgency should be driven by exposure confirmation and normal kernel patch cadence.
Technical view
The issue is in media/rc/igorplugusb. During a USB control request, the request structure can be subject to DMA on some host controllers, so it must follow DMA coherency requirements. The referenced stable commits resolve this by allocating the structure separately. The CVE record does not state confidentiality, integrity, availability impact, or attack preconditions.
Likely exposure
Exposure appears limited to affected Linux kernel versions that include the igorplugusb driver path. Practical exposure depends on whether the vulnerable kernel build ships this driver, whether it is available or loaded, and whether relevant USB hardware or host-controller behavior is present. The source bundle does not provide a complete affected-version range explanation.
Exploitation context
No active exploitation is stated. KEV is false, and the provided sources do not describe public exploitation, proof-of-concept activity, or weaponized use. The available evidence only confirms a kernel fix for DMA coherency handling in this driver.
Researcher notes
The useful technical lead is the DMA coherency rule violation in the USB control-request allocation path. The record is sparse: no CVSS vector, CWE, exploitability notes, or precise distribution-specific affected ranges are provided. Avoid assuming impact beyond the upstream fix description.
Mitigation direction
Track vendor kernel advisories for CVE-2026-46091 and apply fixed kernel updates.
Prioritize systems that expose or use the igorplugusb driver path.
Confirm whether your distribution has backported one of the referenced stable fixes.
If no vendor fix is available, follow vendor guidance for disabling unused affected drivers.
Validation and detection
Inventory Linux kernel versions across managed servers, workstations, and appliances.
Check whether igorplugusb is built, packaged, enabled, or loaded on those systems.
Map deployed kernels against vendor advisories and the referenced upstream stable commits.
Record exceptions where affected kernels remain pending vendor remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46091 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:58 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.