Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98912ALSA: seq: oss: Reject reads that cannot fit the next event

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 3 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b3b4b647313757a275be7f7f9d0415d0a90acf73
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 591226398c1f93bd994678237ff0be229b19d3bb
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 372bec8a01e2ab8eaa6851bdc346ede5f82dba99
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2922cf2583e590f51bed613a6fcd27b9aea83674
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7483fd5f6990f43cc266e94b3f50ce84856ebb97
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 20b8520d1ef996173065f7abdde47b99136c0785
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 611f538253d970f4d152003841544e875828d015
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98912 badge
[![CVE-2026-98912](https://cveledger.app/badge/CVE-2026-98912.svg)](https://cveledger.app/cve/CVE-2026-98912)

Record last updated .