Live › vulnerability › CVE-2026-98912
Go to dashboardIn the Linux kernel's ALSA OSS sequencer, the read path checks whether the next queued event fits the userspace buffer with an inverted comparison. Small reads can copy oversized events and normal events can be skipped, so reads can misbehave or return the wrong result.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the ALSA sequencer OSS emulation code (sound/core/seq/oss) that reads from /dev/sequencer. Hosts without the OSS sequencer in use are unlikely to be reached. The sources do not give affected kernel version ranges, so unknown beyond that.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
ALSA: seq: oss: Reject reads that cannot fit the next event
snd_seq_oss_read() checks whether the next queued OSS sequencer event fits in the remaining userspace buffer before removing it from the read queue.
The check is inverted. It currently stops when the event is smaller than the remaining buffer, so a normal 4-byte event is not copied for an 8-byte read buffer. Conversely, an 8-byte event can be copied for a smaller read count.
Break only when the remaining userspace buffer is smaller than the next event, and report -EINVAL if no complete event has been copied. This prevents an undersized read from looking like end-of-file while leaving the event queued for a later read with a large enough buffer.
This page as .md · .json · in your agent: get_signal("CVE-2026-98912")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.