Live › vulnerability › CVE-2026-98770
Go to dashboardThe Linux kernel's USB MIDI 2.0 gadget driver sized its jack in/out descriptor arrays at MAX_CABLES, but each loop iteration adds two entries, so the arrays overflow when many jacks are configured through configfs. The fix doubles the array sizes to MAX_CABLES * 2; the sources do not state the attacker-controlled impact beyond the out-of-bounds write.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the USB MIDI 2.0 gadget function (f_midi2) built in or loaded, where USB MIDI jacks are configured through configfs. Systems that do not use USB gadget MIDI 2.0 are unlikely to be exposed, but the sources do not confirm this.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: midi2: Fix the jack descriptor array sizes
The jack in/out descriptor arrays in struct f_midi2_usb_config have the size of MAX_CABLES, which look reasonable -- but it turned out to be incorrect. Namely, the entries for those arrays are added from both inputs and outputs, hence for each loop cycle, it adds two, ended up with as twice as the expected size. This inconsistency may result in potential OOB when a large number of jacks are set up via configfs, although the max number of cables (the loop count) is limited to MAX_CABLES.
For addressing it, correct the jack_ins & jack_outs array sizes to twice, MAX_CABLES * 2.
This page as .md · .json · in your agent: get_signal("CVE-2026-98770")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.