Answer in brief
CVE-2025-39935 records a Unknown severity vulnerability in ASoC: codec: sma1307: Fix memory corruption in sma1307_setting_loaded(). 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 | >=576c57e6b4c1d734bcb7cc33dde9a99a9383b520 <cd59ca8f75dbb42a67fcae975c766114644e36c4 || >=576c57e6b4c1d734bcb7cc33dde9a99a9383b520 <78338108b5a856dc98223a335f147846a8a18c51 | cd59ca8f75dbb42a67fcae975c766114644e36c4, 78338108b5a856dc98223a335f147846a8a18c51 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ASoC: codec: sma1307: Fix memory corruption in sma1307_setting_loaded() The sma1307->set.header_size is how many integers are in the header (there are 8 of them) but instead of allocating space of 8 integers we allocate 8 bytes. This leads to memory corruption when we copy data it on the next line: memcpy(sma1307->set.header, data, sma1307->set.header_size * sizeof(int)); Also since we're immediately copying over the memory in ->set.header, there is no need to zero it in the allocator. Use devm_kmalloc_array() to allocate the memory instead.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39935 records a Unknown severity vulnerability in ASoC: codec: sma1307: Fix memory corruption in sma1307_setting_loaded(). 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 | >=576c57e6b4c1d734bcb7cc33dde9a99a9383b520 <cd59ca8f75dbb42a67fcae975c766114644e36c4 || >=576c57e6b4c1d734bcb7cc33dde9a99a9383b520 <78338108b5a856dc98223a335f147846a8a18c51 | cd59ca8f75dbb42a67fcae975c766114644e36c4, 78338108b5a856dc98223a335f147846a8a18c51 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ASoC: codec: sma1307: Fix memory corruption in sma1307_setting_loaded() The sma1307->set.header_size is how many integers are in the header (there are 8 of them) but instead of allocating space of 8 integers we allocate 8 bytes. This leads to memory corruption when we copy data it on the next line: memcpy(sma1307->set.header, data, sma1307->set.header_size * sizeof(int)); Also since we're immediately copying over the memory in ->set.header, there is no need to zero it in the allocator. Use devm_kmalloc_array() to allocate the memory instead.
Quoted source text, attributed separately from HOL analysis.