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-2023-54096soundwire: fix enumeration completion

Description

In the Linux kernel, the following vulnerability has been resolved: soundwire: fix enumeration completion The soundwire subsystem uses two completion structures that allow drivers to wait for soundwire device to become enumerated on the bus and initialised by their drivers, respectively. The code implementing the signalling is currently broken as it does not signal all current and future waiters and also uses the wrong reinitialisation function, which can potentially lead to memory corruption if there are still waiters on the queue. Not signalling future waiters specifically breaks sound card probe deferrals as codec drivers can not tell that the soundwire device is already attached when being reprobed. Some codec runtime PM implementations suffer from similar problems as waiting for enumeration during resume can also timeout despite the device already having been enumerated.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 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-2023-54096, 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 · Deferred3.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 94% of all CVEs (14 Nov 2026)
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 fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 – < 48d1d0ce0782f995fda678508fdae35c5e9593f0
    • affected fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 – < a36b522767f3a72688893a472e80c9aa03e67eda
    • affected fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 – < e1d54962a63b6ec04ed0204a3ecca942fde3a6fe
    • affected fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 – < c5265691cd065464d795de5666dcfb89c26b9bc1
    • affected fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 – < c40d6b3249b11d60e09d81530588f56233d9aa44
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.190 – ≤ 5.10.*
    • unaffected 5.15.126 – ≤ 5.15.*
    • unaffected 6.1.43 – ≤ 6.1.*
    • unaffected 6.4.8 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .