CVE-2026-68184

cdrom: fix stack out-of-bounds read in CDROMVOLCTRL

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: cdrom: fix stack out-of-bounds read in CDROMVOLCTRL mmc_ioctl_cdrom_volume() first reads the audio control mode page into a 32-byte stack buffer with cgc->buflen set to 24. If the device reports a block descriptor, the function increases cgc->buflen to include that descriptor and reads the page again. For CDROMVOLCTRL, the function then builds a MODE SELECT parameter list by moving cgc->buffer forward by offset - 8 bytes. This drops the block descriptor from the outgoing payload and leaves a new 8-byte mode parameter header in front of the audio control page. However, cgc->buflen is left unchanged. With a standard 8-byte block descriptor, cgc->buffer points at buffer + 8 but cgc->buflen remains 32. cdrom_mode_select() therefore asks the low level packet path to write 32 bytes from that adjusted pointer, reading 8 bytes past the end of the 32-byte stack buffer. This is not hit by CDROMVOLREAD, and CDROMVOLCTRL only triggers it on drives that return a non-zero block descriptor length, which helps explain why it has gone unnoticed. The overread is also sent to the device as extra MODE SELECT payload, so it may not produce an obvious local failure. Reduce cgc->buflen by the same amount as the buffer pointer adjustment so the MODE SELECT transfer covers only the intended parameter list.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2652.6.12 ≤ v < 5.15.2162.6.12 ≤ v < 6.1.1832.6.12 ≤ v < 6.12.1012.6.12 ≤ v < 6.18.422.6.12 ≤ v < 6.6.1482.6.12 ≤ v < 7.1.62.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 0329b661349f42f9616f2733da67edffbbb8455d (fixed)
Vendor states this is fixed in 35b68e24c5a69fa4545f46f05f6c849223034cb6 (fixed)
Vendor states this is fixed in 45c65df5339deea3cf204902aac383fe995941a7 (fixed)
Vendor states this is fixed in 7344c84e32413e5c8832f74b8a612b0194e5c051 (fixed)
Vendor states this is fixed in b27e195d4db8dea263050bdbeb11881b2999c9c6 (fixed)
Vendor states this is fixed in d43c5c0c935522deae7339e0c2399365f3bf0016 (fixed)
Vendor states this is fixed in e150c9a10baee55d3bfbc96dbe66b205e8b4fd44 (fixed)
Vendor states this is fixed in f3e2715a150066f09aa82c30fa983fb184ad6dd5 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card