Answer in brief
CVE-2026-72301 records a Unknown severity vulnerability in ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get. 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 | >=544ac8858f249950b4d99c68e538cdc07300528f <8bd715a9d882fe1993bb2aec5eff89fffa946592 || >=544ac8858f249950b4d99c68e538cdc07300528f <0dce240145f47545d2e4b18c6d58033b83e1fd0e || >=544ac8858f249950b4d99c68e538cdc07300528f <ed4f758f34be4c32e02933ac4fa044589d9c1c16 || >=544ac8858f249950b4d99c68e538cdc07300528f <0c4fbdaca225b97122b61b68c5353caa33a253c3 || >=544ac8858f249950b4d99c68e538cdc07300528f <92f90917413bdd6078fefff6f6c83a07bf870b04 || >=544ac8858f249950b4d99c68e538cdc07300528f <1f97760417b5faa60e9642fd0ed61eb17d0b1b39 | 8bd715a9d882fe1993bb2aec5eff89fffa946592, 0dce240145f47545d2e4b18c6d58033b83e1fd0e, ed4f758f34be4c32e02933ac4fa044589d9c1c16, 0c4fbdaca225b97122b61b68c5353caa33a253c3, 92f90917413bdd6078fefff6f6c83a07bf870b04, 1f97760417b5faa60e9642fd0ed61eb17d0b1b39 |
| Linux/Linuxgeneric | 5.18 | 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: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get In sof_ipc3_bytes_put(), the size used for the memcpy is derived from the old data->size already in the buffer, not the incoming new data's size field. If the new data has a different size, the copy length is wrong: it may truncate valid data or copy stale bytes. Similarly, sof_ipc3_bytes_get() checks data->size against max_size without accounting for the sizeof(struct sof_ipc_ctrl_data) offset of the flex array within the allocation. Fix bytes_put to validate and use the incoming data's sof_abi_hdr.size from ucontrol before copying. Fix bytes_get to subtract sizeof(*cdata) from the bounds check to match the actual available space.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72301 records a Unknown severity vulnerability in ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get. 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 | >=544ac8858f249950b4d99c68e538cdc07300528f <8bd715a9d882fe1993bb2aec5eff89fffa946592 || >=544ac8858f249950b4d99c68e538cdc07300528f <0dce240145f47545d2e4b18c6d58033b83e1fd0e || >=544ac8858f249950b4d99c68e538cdc07300528f <ed4f758f34be4c32e02933ac4fa044589d9c1c16 || >=544ac8858f249950b4d99c68e538cdc07300528f <0c4fbdaca225b97122b61b68c5353caa33a253c3 || >=544ac8858f249950b4d99c68e538cdc07300528f <92f90917413bdd6078fefff6f6c83a07bf870b04 || >=544ac8858f249950b4d99c68e538cdc07300528f <1f97760417b5faa60e9642fd0ed61eb17d0b1b39 | 8bd715a9d882fe1993bb2aec5eff89fffa946592, 0dce240145f47545d2e4b18c6d58033b83e1fd0e, ed4f758f34be4c32e02933ac4fa044589d9c1c16, 0c4fbdaca225b97122b61b68c5353caa33a253c3, 92f90917413bdd6078fefff6f6c83a07bf870b04, 1f97760417b5faa60e9642fd0ed61eb17d0b1b39 |
| Linux/Linuxgeneric | 5.18 | 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: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get In sof_ipc3_bytes_put(), the size used for the memcpy is derived from the old data->size already in the buffer, not the incoming new data's size field. If the new data has a different size, the copy length is wrong: it may truncate valid data or copy stale bytes. Similarly, sof_ipc3_bytes_get() checks data->size against max_size without accounting for the sizeof(struct sof_ipc_ctrl_data) offset of the flex array within the allocation. Fix bytes_put to validate and use the incoming data's sof_abi_hdr.size from ucontrol before copying. Fix bytes_get to subtract sizeof(*cdata) from the bounds check to match the actual available space.
Quoted source text, attributed separately from HOL analysis.