Answer in brief
CVE-2026-72257 records a Unknown severity vulnerability in ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5477518b8a0e8a45239646acd80c9bafc4401522 <a164e744d8de1c41049bd9a1452a4b6bbf5bd8bc || >=5477518b8a0e8a45239646acd80c9bafc4401522 <ec369eac0795cfa8f4d3a0cd35a1e8e15f780331 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <2c715f8a1e644ce4c3e8be5b0fd3f1f4704b73b3 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <ca028334343a140efda4b22e53cbce2c5e94a489 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <214af790e3a33ab73587de4c925c60a550eae9c6 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <2e9261761b35f0b67b7487688cd1365f535be0b3 | a164e744d8de1c41049bd9a1452a4b6bbf5bd8bc, ec369eac0795cfa8f4d3a0cd35a1e8e15f780331, 2c715f8a1e644ce4c3e8be5b0fd3f1f4704b73b3, ca028334343a140efda4b22e53cbce2c5e94a489, 214af790e3a33ab73587de4c925c60a550eae9c6, 2e9261761b35f0b67b7487688cd1365f535be0b3 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72257 records a Unknown severity vulnerability in ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5477518b8a0e8a45239646acd80c9bafc4401522 <a164e744d8de1c41049bd9a1452a4b6bbf5bd8bc || >=5477518b8a0e8a45239646acd80c9bafc4401522 <ec369eac0795cfa8f4d3a0cd35a1e8e15f780331 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <2c715f8a1e644ce4c3e8be5b0fd3f1f4704b73b3 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <ca028334343a140efda4b22e53cbce2c5e94a489 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <214af790e3a33ab73587de4c925c60a550eae9c6 || >=5477518b8a0e8a45239646acd80c9bafc4401522 <2e9261761b35f0b67b7487688cd1365f535be0b3 | a164e744d8de1c41049bd9a1452a4b6bbf5bd8bc, ec369eac0795cfa8f4d3a0cd35a1e8e15f780331, 2c715f8a1e644ce4c3e8be5b0fd3f1f4704b73b3, ca028334343a140efda4b22e53cbce2c5e94a489, 214af790e3a33ab73587de4c925c60a550eae9c6, 2e9261761b35f0b67b7487688cd1365f535be0b3 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.