# CVE-2026-80695: hwmon: (sht3x) Fix unaligned accesses

> A local attacker can trigger a kernel panic on strict-alignment architectures by exploiting unaligned memory access in the SHT3x hardware monitoring driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-98075, BELL-CVE-2026-80695, DEBIAN-CVE-2026-80695, GHSA-g772-xp6h-pv6q, UBUNTU-CVE-2026-80695

## What is CVE-2026-80695?

CVE-2026-80695 is a denial of service vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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().

## Which versions are affected by CVE-2026-80695?


## How do I fix CVE-2026-80695?

Apply the vendor's patch.

## Is CVE-2026-80695 being exploited?

There is no known exploitation of CVE-2026-80695 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80695 and fix it if it is affected.

What it is: CVE-2026-80695 is a denial of service vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80695 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80695/ (Markdown: https://insights.sbomify.com/CVE-2026-80695/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80695
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80695
- OSV: https://osv.dev/vulnerability/CVE-2026-80695

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80695/
Summaries are generated and may contain mistakes; the official description above is the record.