Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64240media: rc: igorplugusb: fix control request setup packet

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64240, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 98% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected bc04b8633b375af6ac8a8bb615258b80fe06cdaa – < e823e4294511989f5962e7ad85bf4d179ba74f52
    • affected 81f0fb813e4bf28b3ca28dc218938a32eb48f740 – < 2243ad78ce64d344754260533ae7730c2174a34a
    • affected 0e84aa8fc23c7578f105e3a2160f9d0aa2bed79a – < aa22590a16e51455c6db802c774b31aadc604a9a
    • affected 18d6a7c9e4e63c57157e9a57dd9bf3cd38e4c45a – < 060fca8e098387f949e4eedaf215d952e477ac12
    • affected 0be8fcd9005e3d3b5a61fe34b070a9663adbb4dc – < 0d880d2db9856e94127ab09331363bef59f98005
    • affected 0adac0ee2c42027d80bac02ea9b576a88f8955d3 – < f33b5a61673bd220fdaaf4202cf1013d6d66c943
    • affected a62ca67e3c72fb297dc7c86495ba8f7329d7f150 – < 5cc3f6db72f77d1a8f7f1cf4ac01803927ffdf15
    • affected eac69475b01fe1e861dfe3960b57fa95671c132e – < 171022c7d594c133a45f92357a2a91475edabe20
  • Linux · Linux

    • affected 6.6.140 – < 6.6.143
    • affected 6.12.86 – < 6.12.93
    • affected 6.18.27 – < 6.18.35
    • affected 7.0.4 – < 7.0.12

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64240 badge
[![CVE-2026-64240](https://cveledger.app/badge/CVE-2026-64240.svg)](https://cveledger.app/cve/CVE-2026-64240)

Record last updated .