CVE-2026-98912 — ALSA: seq: oss: Reject reads that cannot fit the next event
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < b3b4b647313757a275be7f7f9d0415d0a90acf73≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 591226398c1f93bd994678237ff0be229b19d3bb≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 372bec8a01e2ab8eaa6851bdc346ede5f82dba99≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 2922cf2583e590f51bed613a6fcd27b9aea83674≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 7483fd5f6990f43cc266e94b3f50ce84856ebb97≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 20b8520d1ef996173065f7abdde47b99136c0785≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 611f538253d970f4d152003841544e875828d015< 5.10.271 and 6 more< 5.15.222< 6.1.189< 6.6.158< 6.12.111< 6.18.53versions not specified by the source |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 23, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
9 on the record
- git.kernel.org/stable/c/372bec8a01e2ab8eaa6851bdc346ede5f82dba99
- github.com/advisories/GHSA-c2vm-8x7j-h34j
- git.kernel.org/stable/c/2922cf2583e590f51bed613a6fcd27b9aea83674
- git.kernel.org/stable/c/611f538253d970f4d152003841544e875828d015
- nvd.nist.gov/vuln/detail/CVE-2026-98912
- git.kernel.org/stable/c/7483fd5f6990f43cc266e94b3f50ce84856ebb97
- git.kernel.org/stable/c/20b8520d1ef996173065f7abdde47b99136c0785
- git.kernel.org/stable/c/b3b4b647313757a275be7f7f9d0415d0a90acf73
- git.kernel.org/stable/c/591226398c1f93bd994678237ff0be229b19d3bb
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99087 dm-integrity: fix NULL pointer dereference when the 'R' flag is used 2h
- Unknown CVE-2026-99086 dm-integrity: validate the superblock on resume 2h
- Unknown CVE-2026-99085 sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler 2h
- Unknown CVE-2026-99084 readdir: take no inode lock on an immutable directory 2h
- Unknown CVE-2026-99083 ksmbd: fix heap out-of-bounds write in krb5_authenticate() 2h
- Unknown CVE-2026-99082 KVM: x86: Use active memslots for the per-vCPU MMIO cache 2h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98912 is "ALSA: seq: oss: Reject reads that cannot fit the next event", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.