KernelScan.io

HIGH Introduced in 4.15

alsa CompatPort UAF

CVE-2026-98742

CVSS 7.0 / 10.0 KernelScan AI

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

01

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Serialize compat port-info ioctls The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex. This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber. Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.

02

Engine v0.9.0

Risk summary

A local attacker with access to the ALSA sequencer device can exploit a race condition in the 32-bit compatibility ioctl path to trigger a use-after-free, potentially achieving kernel privilege escalation or denial of service. The vulnerability affects any system with ALSA sequencer support enabled, including containerized environments where it can be used for container escape.

Affectedsound/core/seq/seq_compat.c (ALSA sequencer)

Vulnerability analysis

The ALSA sequencer's native ioctl path serializes operations using a per-client mutex, but the 32-bit compatibility layer for port-info commands invoked the same handlers without acquiring that lock. This allowed concurrent CREATE_PORT requests to pass a port-count check simultaneously, causing the computed port index to wrap and collide with an existing port. During subsequent subscriber teardown, the duplicate address could resolve to the wrong port and access a subscriber object that had already been freed. The fix adds the missing mutex acquisition around the compat dispatch path, ensuring all port-info operations — native and translated — are serialized identically. Any local user who can open /dev/snd/seq (typically world-accessible) can trigger the race; no special privileges or capabilities are required, making it reachable from containers and unprivileged user namespaces.

03

BranchIntroducedFixed inPatch commit
3.163.16.543.174980768c5d09
3.183.18.943.192c0cce3a5a66
3.23.2.993.314e178c60ba1
4.14.1.504.22db234e163f0
4.144.14.154.15702d92f361f6
4.44.4.1154.5413211dd31cb
4.94.9.784.10fc5c52848e40
5.104.155.10.27395b2e0361c88
5.154.155.15.224—
6.14.156.1.191—
6.124.156.12.113—
6.184.156.18.56—
6.64.156.6.160—
7.24.157.2.10—
mainline4.157.3—
cip/6.124.156.12.114-cip34413211dd31cb

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.114-cip34
cip/6.1Affected — no CIP fix yet (latest 6.1.190-cip62)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)
cip/5.10Affected — no CIP fix yet (latest 5.10.272-cip79)
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.272-cip79-rt35)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip137)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip137-rt51)
cip/4.4Affected — no CIP fix yet (latest 4.4.302-cip116)
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)