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-74387ALSA: seq: midi: Serialize output teardown with event_input

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: midi: Serialize output teardown with event_input event_process_midi() borrows msynth->output_rfile.output and then passes the substream to dump_midi() and snd_rawmidi_kernel_write() without synchronizing with the output open/close transition. midisynth_use() also publishes output_rfile before snd_rawmidi_output_params() has finished. The last midisynth_unuse() can therefore release the same rawmidi file and free substream->runtime before snd_rawmidi_kernel_write1() takes its runtime buffer reference. That leaves the event_input path using a stale substream or runtime and can end in a NULL-deref or use-after-free. Fix this with two pieces of synchronization. Keep a short IRQ-safe spinlock only for publishing or clearing output_rfile and for pairing the output snapshot with an snd_use_lock_t reference. Once event_process_midi() has taken that in-flight reference, it drops the spinlock before calling snd_seq_dump_var_event(), dump_midi(), or snd_rawmidi_kernel_write(). midisynth_unuse() now detaches the visible rawmidi file under the same spinlock, waits for the in-flight writers to drain, and only then drains and releases the saved file. midisynth_use() likewise opens into a local snd_rawmidi_file and publishes it only after snd_rawmidi_output_params() succeeds. The buggy scenario involves two paths, with each column showing the order within that path: event_input path: last unuse path: 1. event_process_midi() snapshots 1. midisynth_unuse() starts output_rfile.output. tearing down output_rfile. 2. dump_midi() reaches 2. snd_rawmidi_kernel_release() snd_rawmidi_kernel_write() closes the output file. before runtime is pinned. 3. close_substream() frees 3. The callback keeps using substream->runtime. the borrowed substream. Validation reproduced this kernel report: KASAN null-ptr-deref in snd_rawmidi_kernel_write1+0x56/0x360 RIP: 0033:0x7fde7dd0837f RIP: 0010:snd_rawmidi_kernel_write1+0x56/0x360

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months 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

CVSS scores of CVE-2026-74387, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f5d470b808bc01f70978e22e595c6f7768313406
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 936641af564c3d92721704b781e36aaf223efdd2
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 718f6a56b40875f19e6915799044a02df9abfd52
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 11165fe2c5ea0516debe486d91df67abbe36905e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d6fd2afb137f52bf00c5210cc44d08ed54dcffb4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ef7607ab1c8adc6258fb1b27d08e26aecdc18a58
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .