# CVE-2026-68356: watchdog: airoha: Prevent division by zero when clock frequency is zero

> A division by zero in the Airoha watchdog driver causes a kernel crash if the clock frequency is zero, leading to denial of service.

- **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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68356, DEBIAN-CVE-2026-68356, GHSA-cq6f-qj9v-h84p, UBUNTU-CVE-2026-68356

## What is CVE-2026-68356?

CVE-2026-68356 is a denial of service vulnerability in Linux, published on 10 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:

watchdog: airoha: Prevent division by zero when clock frequency is zero

clk_get_rate() can return 0 when the clock provider is not properly
configured or the clock is unmanaged. The driver uses wdt_freq as a
divisor directly in airoha_wdt_probe() to compute max_timeout and in
airoha_wdt_get_timeleft() to compute the remaining time, which results
in a division by zero.

Add a check for wdt_freq == 0 in probe and return -EINVAL with
dev_err_probe() to prevent the division by zero and provide a
diagnostic message.

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


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

Apply the vendor's patch.

## Is CVE-2026-68356 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68356 is a denial of service vulnerability in Linux, published on 10 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-68356 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-68356/ (Markdown: https://insights.sbomify.com/CVE-2026-68356/index.md)
```

## Sources

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

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