CVE-2026-64483

ALSA: firewire: isight: bound the sample count to the packet payload

N/A
Published: July 25, 2026 at 08:51 AM UTC
Updated: August 17, 2026 at 05:17 AM 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: ALSA: firewire: isight: bound the sample count to the packet payload isight_packet() takes the frame count from the device iso packet and checks it only against the device claimed iso length. count = be32_to_cpu(payload->sample_count); if (likely(count <= (length - 16) / 4)) isight_samples(isight, payload->samples, count); length is the iso header data_length. It can be up to 0xffff. So the gate allows a count up to about 16379. isight_samples() then copies count frames out of payload->samples into the PCM DMA buffer. payload->samples holds only 2 * MAX_FRAMES_PER_PACKET values. The device multiplexes two samples per frame. A count past MAX_FRAMES_PER_PACKET reads past the payload. A count past the buffer size writes past runtime->dma_area. The smallest PCM buffer is larger than MAX_FRAMES_PER_PACKET. Bounding the count to MAX_FRAMES_PER_PACKET keeps both the read and the write in range. A malicious or faulty Apple iSight on the FireWire bus reaches this during a normal capture. Add the MAX_FRAMES_PER_PACKET bound to the gate.

Affected

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

3.0 ≤ v < 5.10.2613.0 ≤ v < 5.15.2123.0 ≤ v < 6.1.1783.0 ≤ v < 6.12.963.0 ≤ v < 6.18.393.0 ≤ v < 6.6.1453.0 ≤ v < 7.1.43.0 ≤ v < 7.23.03a691b28a0ca3cf4d9010c6158318159e0275d2c
Vendor states this is fixed in 24423e0a9251d348c3f1fb0bb0e61b879e1e976c (fixed)
Vendor states this is fixed in 29b9667982e4df2ed7744f86b1144f8bb58eb698 (fixed)
Vendor states this is fixed in 31a01b70bb90e3ef3147f308e2ea899e1d2485ca (fixed)
Vendor states this is fixed in 31da82b9676c6b112e7c72c7529e6812b919742a (fixed)
Vendor states this is fixed in 3ed2fa1ed8cc65f910b8bbc0be3cc366b30f8478 (fixed)
Vendor states this is fixed in 57e4d9043afc1eaddee8f50d11def6e65415d273 (fixed)
Vendor states this is fixed in 8e48a29813df8dd71503800b7acf69c12c035045 (fixed)
Vendor states this is fixed in ebbffacda6733dcbcef601b5b523460f8d8b671e (fixed)
Vendor states this is fixed in 3.0 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (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