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-2025-38078ALSA: pcm: Fix race of buffer access at PCM OSS layer

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix race of buffer access at PCM OSS layer The PCM OSS layer tries to clear the buffer with the silence data at initialization (or reconfiguration) of a stream with the explicit call of snd_pcm_format_set_silence() with runtime->dma_area. But this may lead to a UAF because the accessed runtime->dma_area might be freed concurrently, as it's performed outside the PCM ops. For avoiding it, move the code into the PCM core and perform it inside the buffer access lock, so that it won't be changed during the operation.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 16 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-2025-38078, 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 · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (19 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 – < c0e05a76fc727929524ef24a19c302e6dd40233f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8170d8ec4efd0be352c14cb61f374e30fb0c2a25
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 10217da9644ae75cea7330f902c35fc5ba78bbbf
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f3e14d706ec18faf19f5a6e75060e140fea05d4a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 74d90875f3d43f3eff0e9861c4701418795d3455
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bf85e49aaf3a3c5775ea87369ea5f159c2148db4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < afa56c960fcb4db37f2e3399f28e9402e4e1f470
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 93a81ca0657758b607c3f4ba889ae806be9beb73
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.185 – ≤ 5.15.*
    • unaffected 6.1.141 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.31 – ≤ 6.12.*
    • unaffected 6.14.9 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .