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-2022-49733ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC There is a small race window at snd_pcm_oss_sync() that is called from OSS PCM SNDCTL_DSP_SYNC ioctl; namely the function calls snd_pcm_oss_make_ready() at first, then takes the params_lock mutex for the rest. When the stream is set up again by another thread between them, it leads to inconsistency, and may result in unexpected results such as NULL dereference of OSS buffer as a fuzzer spotted recently. The fix is simply to cover snd_pcm_oss_make_ready() call into the same params_lock mutex with snd_pcm_oss_make_ready_locked() variant.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 17 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-2022-49733, 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
CISA-ADPADP (enrichment)3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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.16% · top 95% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 – < 4051324a6dafd7053c74c475e80b3ba10ae672b0
    • affected e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 – < fce793a056c604b41a298317cf704dae255f1b36
    • affected e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 – < 8015ef9e8a0ee5cecfd0cb6805834d007ab26f86
    • affected e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 – < 723ac5ab2891b6c10dd6cc78ef5456af593490eb
    • affected e3a5d59a17e9a42e3f3e0e37342b2679bab2ff43 – < 8423f0b6d513b259fdab9c9bf4aaa6188d054c2d
  • Linux · Linux

    • affected 2.6.20
    • unaffected < 2.6.20
    • unaffected 5.4.215 – ≤ 5.4.*
    • unaffected 5.10.148 – ≤ 5.10.*
    • unaffected 5.15.68 – ≤ 5.15.*
    • unaffected 5.19.9 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .