CVE-2026-64029

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-45602 (ENISA EUVD) · GHSA-93ph-845p-qqq3 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: seq: Serialize UMP output teardown with event_input

seq_ump_process_event() borrows client->out_rfile.output without synchronizing with the first-open and last-close transition in seq_ump_client_open() and seq_ump_client_close().

The last output unuse can therefore drop opened[STR_OUT] to zero and release the rawmidi file while an in-flight event_input callback is still inside snd_rawmidi_kernel_write(). That leaves the rawmidi substream runtime exposed to teardown before the write path has taken its own buffer reference.

Add a per-client rwlock for the event_input-visible output file. Publish a newly opened output file under the write side, and hold the read side from the output lookup through snd_rawmidi_kernel_write(). The last output close copies and clears the visible output file under the write side, then drops the lock and releases the saved rawmidi file. Use IRQ-safe rwlock guards because event_input can also be reached from atomic sequencer delivery.

The buggy scenario involves two paths, with each column showing the order within that path:

path A label: event_input path path B label: last unuse path

  • seq_ump_process_event() reads 1. seq_ump_client_close()
client->out_rfile.output. drops opened[STR_OUT] to zero.
  • snd_rawmidi_kernel_write1() 2. snd_rawmidi_kernel_release()
has not yet pinned runtime. closes the output file.
  • The writer continues using 3. close_substream() frees
the borrowed substream. substream->runtime.

This keeps the output substream and runtime alive for the full event_input write while keeping rawmidi release outside the rwlock.

KASAN reproduced this as a slab-use-after-free in snd_rawmidi_kernel_write1(), with allocation through seq_ump_use()/snd_seq_port_connect() and free through seq_ump_unuse()/snd_seq_port_disconnect().

Validation reproduced this kernel report: KASAN slab-use-after-free in snd_rawmidi_kernel_write1+0x9d/0x400 RIP: 0033:0x7f5528af837f Read of size 8 Call trace: dump_stack_lvl+0x73/0xb0 (?:?) print_report+0xd1/0x650 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x1a7/0x340 (?:?) kasan_complete_mode_report_info+0x64/0x200 (?:?) kasan_report+0xf7/0x130 (?:?) snd_rawmidi_kernel_write1+0x9d/0x400 (?:?) __asan_load8+0x82/0xb0 (?:?) update_stack_state+0x1ef/0x2d0 (?:?) snd_rawmidi_kernel_write+0x1a/0x20 (?:?) seq_ump_process_event+0xd4/0x120 (sound/core/seq/seq_ump_client.c:82) __snd_seq_deliver_single_event+0x8a/0xe0 (?:?) snd_seq_deliver_from_ump+0x2b2/0xd60 (?:?) lock_acquire+0x14e/0x2e0 (?:?) find_held_lock+0x31/0x90 (?:?) snd_seq_port_use_ptr+0xa6/0xe0 (?:?) __kasan_check_write+0x18/0x20 (?:?) do_raw_read_unlock+0x32/0xa0 (?:?) _raw_read_unlock+0x26/0x50 (?:?) snd_seq_deliver_single_event+0x45c/0x4b0 (?:?) snd_seq_deliver_event+0x10d/0x1b0 (?:?) snd_seq_client_enqueue_event+0x192/0x240 (?:?) snd_seq_write+0x2cd/0x450 (?:?) apparmor_file_permission+0x20/0x30 (?:?) security_file_permission+0x51/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) __fget_files+0x12b/0x220 (?:?) lock_release+0xc8/0x2a0 (?:?) __rcu_read_unlock+0x74/0x2d0 (?:?) __fget_files+0x135/0x220 (?:?) ksys_write+0x15a/0x180 (?:?) rcu_is_watching+0x24/0x60 (?:?) __x64_sys_write+0x46/0x60 (?:?) x64_sys_call+0x7d/0x20d0 (?:?) do_syscall_64+0xc1/0x360 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Jul 21, 2026
Patch available.
Web page

ALSA: seq: Serialize UMP output teardown with event_input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef46b616a4c219185bbf10ebcbacb571583fd0e4
Web page

ALSA: seq: Serialize UMP output teardown with event_input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ba1c4ddbb1c67d34bb440aecb9f5690ed3f64cb
Web page

ALSA: seq: Serialize UMP output teardown with event_input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60a1969fae6209644698fca91c185d153674f631
Web page

ALSA: seq: Serialize UMP output teardown with event_input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3aab4a58d23fb22dac5b558bbe5df1a8dad00b4b
Web page

ALSA: seq: Serialize UMP output teardown with event_input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cb1ad795570167558530d6194297ac2396a1991

Vendor Advisories for CVE-2026-64029(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1064.67) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1064.67+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1066.67~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1061.64) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-139.139.1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1036.37) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1067.75+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1067.75~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2053.55) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-27ubuntu
redhatkernel-0:6.12.0-211.56.1.el10_22026-09-17redhat
redhatkernel-0:5.14.0-687.49.1.el9_82026-09-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 333 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 233 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-10-30 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-10-29 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-10-28 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-27 18:43 UTCEG score recompute
  6. 2026-10-27 18:43 UTCVendor advisory
  7. 2026-10-27 18:42 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-25 14:13 UTCEG score recompute
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-10-21 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-19 21:38 UTCEG score recompute
  14. 2026-10-19 21:38 UTCVendor advisory
  15. 2026-10-19 21:38 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-19 20:36 UTCEG score recompute
  17. 2026-10-19 20:36 UTCVendor advisory
  18. 2026-10-19 20:35 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-18 03:23 UTCEG score recompute
  20. 2026-10-16 17:23 UTCEG score recompute
  21. 2026-10-16 17:23 UTCVendor advisory
  22. 2026-10-16 17:23 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-10-16 15:56 UTCEG score recompute
  25. 2026-10-16 15:56 UTCVendor advisory
Show 75 more
  1. 2026-10-16 15:56 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-13 15:46 UTCEG score recompute
  5. 2026-10-13 15:46 UTCVendor advisory
  6. 2026-10-13 15:46 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-13 11:47 UTCEG score recompute
  8. 2026-10-13 11:47 UTCVendor advisory
  9. 2026-10-13 11:47 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-12 15:48 UTCEG score recompute
  12. 2026-10-11 19:33 UTCEG score recompute
  13. 2026-10-11 16:48 UTCEG score recompute
  14. 2026-10-11 14:09 UTCEG score recompute
  15. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-10-01 08:45 UTCEG score recompute
  27. 2026-10-01 08:45 UTCVendor advisory
  28. 2026-10-01 08:44 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-09-28 07:24 UTCEG score recompute
  32. 2026-09-28 07:24 UTCVendor advisory
  33. 2026-09-28 07:24 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  35. 2026-09-24 03:38 UTCEG score recompute
  36. 2026-09-24 03:38 UTCVendor advisory
  37. 2026-09-24 03:38 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-09-23 02:01 UTCEG score recompute
  40. 2026-09-23 02:01 UTCVendor advisory
  41. 2026-09-23 02:01 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-09-18 04:18 UTCEG score recompute
  45. 2026-09-18 04:18 UTCVendor advisory
  46. 2026-09-18 04:18 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-09-17 05:29 UTCEG score recompute
  48. 2026-09-17 05:29 UTCVendor advisory
  49. 2026-09-17 05:29 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-09-16 12:58 UTCEG score recompute
  52. 2026-09-16 12:58 UTCVendor advisory
  53. 2026-09-16 12:58 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-09-14 05:35 UTCVendor advisory
  56. 2026-09-14 05:35 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-13 18:28 UTCEG score recompute
  58. 2026-09-13 18:28 UTCVendor advisory
  59. 2026-09-13 18:28 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-09-13 07:03 UTCVendor advisory
  61. 2026-09-13 07:03 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-12 19:41 UTCEG score recompute
  63. 2026-09-12 19:41 UTCVendor advisory
  64. 2026-09-12 19:41 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-12 06:06 UTCVendor advisory
  66. 2026-09-12 06:06 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-11 18:46 UTCEG score recompute
  68. 2026-09-11 18:46 UTCVendor advisory
  69. 2026-09-11 18:46 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  71. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  72. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  73. 2026-09-07 23:19 UTCEG score recompute
  74. 2026-09-07 23:19 UTCVendor advisory
  75. 2026-09-07 23:19 UTCGHSA enrichmentGHSA-93ph-845p-qqq3 · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64029?
CVE-2026-64029 is a high-severity vulnerability; its CVE record was published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Serialize UMP output teardown with event_input seq_ump_process_event() borrows client->out_rfile.output without synchronizing with the first-open and last-close transition in seq_ump_client_open() and…
When was the CVE record for CVE-2026-64029 published?
The CVE record for CVE-2026-64029 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-64029 actively exploited?
CVE-2026-64029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64029?
CVE-2026-64029 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64029?
A fix for CVE-2026-64029 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64029 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64029

Explore →

Is Your Infrastructure Affected by CVE-2026-64029?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs