CVE-2026-74278

Unknown

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix kernel heap address leak in bounce_error_event() The comment above bounce_error_event() documents that user clients should receive SNDRV_SEQ_EVENT_BOUNCE with the original event embedded as variable-length data, while kernel clients should receive SNDRV_SEQ_EVENT_KERNEL_ERROR with a quoted kernel pointer. However, the implementation unconditionally uses SNDRV_SEQ_EVENT_KERNEL_ERROR with data.quote.event set to the raw struct snd_seq_event pointer for all clients. When a bounce error event is delivered to a USER_CLIENT via snd_seq_read(), the kernel heap address in data.quote.event is exposed to userspace through copy_to_user() in the fixed-length branch. This is a distinct leak path from the one addressed by commit 705dd6dcbc0e ("ALSA: seq: Clear variable event pointer on read"), which sanitizes data.ext.ptr in the variable-length branch of snd_seq_read(). The bounce_error_event() leak uses fixed-length events that take the else branch where no sanitization occurs. Differentiate the bounce event by client type. For USER_CLIENT, send SNDRV_SEQ_EVENT_BOUNCE with SNDRV_SEQ_EVENT_LENGTH_VARIABLE and data.ext pointing to the original event. The variable-length path in snd_seq_event_dup() copies the event data into chained cells, and snd_seq_expand_var_event() copies only the content -- never the pointer -- to userspace. For KERNEL_CLIENT, keep the existing SNDRV_SEQ_EVENT_KERNEL_ERROR behavior with the quoted pointer.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedAug 15, 2026
First seenAug 15, 2026

How to fix

Update
  • Linux Linux05e2358fec8812c37516ccea63bc4b9956d864ba, eae296065ede41a24040e6a7c909ec970f78b4eb, 93d260ce43a81df579c98bee92b91316df9c1c57, dae23c545eb5a2be3b27a82fd0f611894fb8ab69, 0527a56cb327021cb73167cfddf0e49efa043500, efc86691e4d8083d9e380ea95042c2cf679f65fd or later

Affected products

ProductAffected versionsFixed in
Linux Linux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ≤ v < 05e2358fec8812c37516ccea63bc4b9956d864ba, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ≤ v < eae296065ede41a24040e6a7c909ec970f78b4eb, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ≤ v < 93d260ce43a81df579c98bee92b91316df9c1c57, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ≤ v < dae23c545eb5a2be3b27a82fd0f611894fb8ab69, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ≤ v < 0527a56cb327021cb73167cfddf0e49efa043500, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ≤ v < efc86691e4d8083d9e380ea95042c2cf679f65fd, 2.6.1205e2358fec8812c37516ccea63bc4b9956d864ba, eae296065ede41a24040e6a7c909ec970f78b4eb, 93d260ce43a81df579c98bee92b91316df9c1c57, dae23c545eb5a2be3b27a82fd0f611894fb8ab69, 0527a56cb327021cb73167cfddf0e49efa043500, efc86691e4d8083d9e380ea95042c2cf679f65fd

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.