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-98314ALSA: pcm: set timer->private_data before registering the PCM timer

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: set timer->private_data before registering the PCM timer snd_pcm_timer_init() calls snd_device_register() to link the new struct snd_timer into the global timer list while it still carries hw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop), and only afterwards sets timer->private_data = substream. Once the timer is on the list under register_mutex, a concurrent reader can already reach it through the same mutex and invoke these callbacks. /proc/asound/timers does this via c_resolution(), and snd_timer_open()+snd_timer_start() reach start()/stop() the same way. All three dereference timer->private_data, which for this brief window is NULL, giving a NULL-pointer dereference: substream = timer->private_data; return substream->runtime ? ... // substream is NULL Move the private_data/private_free assignment before snd_device_register() so the timer is never visible on the list without its private_data set. On the snd_device_register() failure path, private_free() (snd_pcm_timer_free()) can now run, but it only does substream->timer = NULL, which is already NULL at that point since substream->timer is set to the new timer just once, after a successful registration -- so the failure path stays safe.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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.18% · top 92% of all CVEs (16 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 – < 27f167e117eca310661fbcbacb352ea08face067
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 555d168bd98daa46daccc68c908201388c834293
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8c869d5cf5affb20994bdbb60e7d46d65c91b55f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 686c7a6af1eea8d2a919303e4c6bbec3de79dbdc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d63f5a9f8121fb43c798056d7dd34c58f47185d7
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0b349249d572633d7c8cdeb917623d1676a2b7c3
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1e713f9bb2ac583521f06b0eb4e22440b1e3d078
  • 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.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .