Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99609

ALSA: usx2y: Require a buffer of two URBs

No exploitation reported by the sources we read.

  • Published2026-11-20
  • Fixed in7.3.5 · 6.18.64 · 6.12.118

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: Require a buffer of two URBs usx2y_urb_capt_retire() wraps the ring buffer once per packet and usx2y_urb_play_prepare() once per URB of nr_of_packs() packets of up to 50 frames. Both assume that the data fits in the buffer, and the hw constraints only require about two 1 ms periods, so a packet larger than the buffer on capture, or a URB larger than the buffer on playback, violates that assumption. Constrain SNDRV_PCM_HW_PARAM_BUFFER_SIZE in snd_usx2y_pcm_open() to at least two URBs, 2 * nr_of_packs() * 50 frames, for both directions. The bound is in frames and derived from the driver's own packet limit, so it does not read the endpoint, whose altsetting is only selected in prepare. Two URBs rather than one, because the position advances by a URB on playback and only moves when a URB is less than the whole buffer. Keep a guard in usx2y_urb_capt_retire() that drops a packet larger than the buffer, for the case the constraint makes unreachable. With nrpacks above about 163 (S16_LE) or 109 (S24_3LE) the bound exceeds the 64 KiB buffer the substream preallocates (twice that with the preallocation raised to its 128 KiB maximum), so hw_params fails for those module settings. That is intended: the driver cannot be safe with a URB larger than half the largest buffer. Reproduced on 7.3-rc7 with a USB/IP device presenting the US-122 interface layout and 1024-byte packets into a 512-byte capture buffer: BUG: KASAN: out-of-bounds in i_usx2y_urb_complete+0x1285/0x1ac0 Read of size 18446744073709551104 at addr ffff88800e448800 by task vhci_rx/83 Tested on 7.3-rc7 with the same device, S16_LE at 44100 Hz, nrpacks 4, so the bound is 400 frames. A 128-frame capture buffer and a 200-frame playback buffer are refused at hw_params with EINVAL. A 400-frame buffer streams for 30 s in each direction with the position advancing inside the buffer and no KASAN report; the capture guard did not fire. The same 400-frame capture buffer with S24_3LE, which selects altsetting 2 in prepare, streams for 30 s with the same result.

Timeline

dates in UTC
  1. 2026-11-2005:49CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.57.3.5
6.x≥ 6.13.0, < 6.18.646.18.64
6.12≥ 2.6.12, < 6.12.1186.12.118

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 44c6971a79efdb46cd5c9f492f0ad65aafe05addfixed in 44c6971a79efdb46cd5c9f492f0ad65aafe05addgit
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 5356d89f5e581dc207c7a607fe585d3e1cb2471cfixed in 5356d89f5e581dc207c7a607fe585d3e1cb2471cgit
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 824fdf771cb7cbe9ae50eaec588eaf1acee6da94fixed in 824fdf771cb7cbe9ae50eaec588eaf1acee6da94git
    • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4cbb826b3b36df6c275454287ba1df4564a5370bfixed in 4cbb826b3b36df6c275454287ba1df4564a5370bgit
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 2.6.12no fix stated

    Not affected < 2.6.12 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kernelAzure Linux:3all versions · no fixed version listed
  • linuxDebian:14all versions · no fixed version listed
  • linuxDebian:13all versions · fixed in 6.12.118-1
  • linuxDebian:12all versions · no fixed version listed
  • linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
  • linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed

Vendor advisories

  • CVE-2026-99609 Red Hat Product Security

    kernel: kernel: Denial of Service via out-of-bounds memory access in ALSA usx2y driver

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-20
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-9rmm-m9vg-p97f

Frequently asked questions

What is CVE-2026-99609?

In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: Require a buffer of two URBs usx2y_urb_capt_retire() wraps the ring buffer once per packet and usx2y_urb_play_prepare() once per URB of nr_of_packs() packets of up to 50 frames. Both assume that the data fits in the buffer, and the hw constraints only require about two 1 ms periods, so a packet larger than the buffer on capture, or a URB larger than the buffer on playback, violates that assumption. Constrain SNDRV_PCM_HW_PARAM_BUFFER_SIZE in snd_usx2y_pcm_open() to at least two URBs, 2 * nr_of_packs() * 50 frames, for both directions. The bound is in frames and derived from the driver's own packet limit, so it does not read the endpoint, whose altsetting is only selected in prepare. Two URBs rather than one, because the position advances by a URB on playback and only moves when a URB is less than the whole buffer. Keep a guard in usx2y_urb_capt_retire() that drops a packet larger than the buffer, for the case the constraint makes unreachable. With nrpacks above about 163 (S16_LE) or 109 (S24_3LE) the bound exceeds the 64 KiB buffer the substream preallocates (twice that with the preallocation raised to its 128 KiB maximum), so hw_params fails for those module settings. That is intended: the driver cannot be safe with a URB larger than half the largest buffer. Reproduced on 7.3-rc7 with a USB/IP device presenting the US-122 interface layout and 1024-byte packets into a 512-byte capture buffer: BUG: KASAN: out-of-bounds in i_usx2y_urb_complete+0x1285/0x1ac0 Read of size 18446744073709551104 at addr ffff88800e448800 by task vhci_rx/83 Tested on 7.3-rc7 with the same device, S16_LE at 44100 Hz, nrpacks 4, so the bound is 400 frames. A 128-frame capture buffer and a 200-frame playback buffer are refused at hw_params with EINVAL. A 400-frame buffer streams for 30 s in each direction with the position advancing inside the buffer and no KASAN report; the capture guard did not fire. The same 400-frame capture buffer with S24_3LE, which selects altsetting 2 in prepare, streams for 30 s with the same result.

Is CVE-2026-99609 actively exploited?

Active exploitation of CVE-2026-99609 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99609?

CVE-2026-99609 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record