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-72257ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback When q6apm_free_fragments() is called it frees rx_data.buf/tx_data.buf and sets them to NULL under graph->lock. A late DSP buffer-done response can race with this: graph_callback() passes the !graph->ar_graph guard (not yet NULL), acquires the lock, but then dereferences a now-NULL buf pointer to read buf[token].phys, crashing at virtual address 0x10. Add a NULL check for buf inside the mutex-protected section in both the write-done (DATA_CMD_RSP_WR_SH_MEM_EP_DATA_BUFFER_DONE_V2) and read-done (DATA_CMD_RSP_RD_SH_MEM_EP_DATA_BUFFER_V2) handlers and bail out cleanly if buffers have already been freed. This problem is only shown up recently while apr bus was updated to process the commands per service rather from single global queue.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 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.21% · top 88% of all CVEs (18 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 5477518b8a0e8a45239646acd80c9bafc4401522 – < a164e744d8de1c41049bd9a1452a4b6bbf5bd8bc
    • affected 5477518b8a0e8a45239646acd80c9bafc4401522 – < ec369eac0795cfa8f4d3a0cd35a1e8e15f780331
    • affected 5477518b8a0e8a45239646acd80c9bafc4401522 – < 2c715f8a1e644ce4c3e8be5b0fd3f1f4704b73b3
    • affected 5477518b8a0e8a45239646acd80c9bafc4401522 – < ca028334343a140efda4b22e53cbce2c5e94a489
    • affected 5477518b8a0e8a45239646acd80c9bafc4401522 – < 214af790e3a33ab73587de4c925c60a550eae9c6
    • affected 5477518b8a0e8a45239646acd80c9bafc4401522 – < 2e9261761b35f0b67b7487688cd1365f535be0b3
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .