CVE-2026-64240
Last modified
CVE-2026-64240 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: media: rc: igorplugusb: fix control request setup packet Commit eac69475b01f ("media: rc: igorplugusb: heed coherency rules") changed the control request storage from an embedded struct to an allocated pointer so it can obey DMA coherency rules. However, the driver still passes &ir->request to usb_fill_control_urb(). That points the URB setup packet at the pointer field itself rather than at the allocated struct usb_ctrlrequest. USB core then interprets pointer bytes as the setup packet. This can produce an invalid bRequestType and trigger the control direction warning reported by syzbot: usb 2-1: BOGUS control dir, pipe 80003580 doesn't match bRequestType 0 Pass ir->request itself as the setup packet.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: media: rc: igorplugusb: fix control request setup packet Commit eac69475b01f ("media: rc: igorplugusb: heed coherency rules") changed the control request storage from an embedded struct to an allocated pointer so it can obey DMA coherency rules. However, the driver still passes &ir->request to usb_fill_control_urb(). That points the URB setup packet at the pointer field itself rather than at the allocated struct usb_ctrlrequest. USB core then interprets pointer bytes as the setup packet. This can produce an invalid bRequestType and trigger the control direction warning reported by syzbot: usb 2-1: BOGUS control dir, pipe 80003580 doesn't match bRequestType 0 Pass ir->request itself as the setup packet.
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.140, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.12.86, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.18.27, < 6.18.35 | — |
| Linux | Linux Kernel | >= 7.0.4, < 7.0.12 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64240?
How severe is CVE-2026-64240?
How do I fix CVE-2026-64240?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64235In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64236In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64237In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64238In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64239In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6424Use-after-free vulnerability in ESET Linux products potentia…6.7
- CVE-2026-64241In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64242In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64243In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64244In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64245In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64246In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64240?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
