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-90033ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output()

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() The snd_usbmidi_us122l_output() picks a count of 2 on anything slower than high speed and never relates it to ep->max_transfer. The URB buffer holds exactly max_transfer bytes, so a device declaring a one byte bulk endpoint takes two bytes from snd_rawmidi_transmit(), and the memset that pads the rest computes 1 - 2 in int and wraps to SIZE_MAX. Only 0x800e and 0x800f are pinned to nine bytes. The US-122MKII at 0x0644:0x8021 falls to the default and takes usb_maxpacket(), which the USB core only clamps downward. The akai and novation output ops in this file were given the same guard recently. Do the same here.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < 5538daf2a5cc80ac3f3e913c0db045d92d995d40
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < a441a8e52148c91c2f2a91f42e3b9bc961a13a4b
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < 2dae0e3a59e31f78222279d544b98e747cd1fbff
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < 1d4add2b832b56f81bb0eab065ec35c610343018
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < de6d252f115be887a701c09a05cdb076f3a590c9
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < 9392a2c346762ffee8edd1ba8bac50d2e24a2ed7
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < 9d81885d97cba7796d1f8edc88f2499c8296f5b9
    • affected 030a07e441296c372f946cd4065b5d831d8dc40c – < e4637ce34607f1733a34a57294966d26b263e626
  • Linux · Linux

    • affected 2.6.28
    • unaffected < 2.6.28
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .