Answer in brief
CVE-2026-80695 records a Unknown severity vulnerability in hwmon: (sht3x) Fix unaligned accesses. 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 | >=7c84f7f80d6fcea36246b793d06c3555ca53ddcd <81529add4a2e3cca9240e0e2342973d62f88f02e || >=7c84f7f80d6fcea36246b793d06c3555ca53ddcd <c498adfd4c3e85306ccdc19b76e639bfc215f0e7 || >=7c84f7f80d6fcea36246b793d06c3555ca53ddcd <1fb41650bc3e14d2a5ddb4bb25e96811e5afe881 || >=7c84f7f80d6fcea36246b793d06c3555ca53ddcd <f46d5ab43a572b84773015a76966f5da56fc1748 | 81529add4a2e3cca9240e0e2342973d62f88f02e, c498adfd4c3e85306ccdc19b76e639bfc215f0e7, 1fb41650bc3e14d2a5ddb4bb25e96811e5afe881, f46d5ab43a572b84773015a76966f5da56fc1748 |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
In the Linux kernel, the following vulnerability has been resolved: hwmon: (sht3x) Fix unaligned accesses Sashiko reports: In sht3x_update_client(), the 16-bit temperature and humidity values are extracted from a stack-allocated byte array using be16_to_cpup(). The pointers passed to this function are calculated as buf and buf + 3. Since the difference between the two pointers is an odd number of bytes, at least one of them is guaranteed to be at an unaligned offset. This will trigger an alignment fault on strict-alignment architectures such as ARMv5 or SPARC, resulting in a kernel panic. Fix the problem by using get_unaligned_be16() instead of be16_to_cpup(), and put_unaligned_be16() instead of cpu_to_be16().
Quoted source text, attributed separately from HOL analysis.