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-50016ASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 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-50016, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 87% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e3105c0ccc3e706584030159b6fde54cab2f8aef – < 230f646085d17a008b609eb8fe8befb8811868f0
    • affected e3105c0ccc3e706584030159b6fde54cab2f8aef – < acacd9eefd0def5a83244d88e5483b5f38ee7287
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 5.19.4 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References

References2

Sources

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

Badge for a README or a ticket

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

Record last updated .