Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.

Published 19 Jul 2026Updated 2 Oct 20264 sources
CVSS 7.8

What happened

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.

Affected versions

Linux: 060d77b9c04acd7aef60790398a53f731db8c8fe through before 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce (git); 060d77b9c04acd7aef60790398a53f731db8c8fe through before e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c (git); 060d77b9c04acd7aef60790398a53f731db8c8fe through before be387230dc22d870afd0e5d35912b07c2bc323bd (git); 060d77b9c04acd7aef60790398a53f731db8c8fe through before 4cc54bdd54b337e77115be5b55577d1c58608eae (git); 2.6.17 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.