# CVE-2026-72414: net: dsa: sja1105: round up PTP perout pin duration

> A local attacker can cause a kernel crash via division by zero in the SJA1105 DSA driver by providing small PTP period values.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72414, DEBIAN-CVE-2026-72414, GHSA-qh8g-7fvq-cf33, UBUNTU-CVE-2026-72414

## What is CVE-2026-72414?

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

net: dsa: sja1105: round up PTP perout pin duration

pin_duration is converted from the user-provided period to SJA1105
clock ticks and is later passed as the cycle_time argument to
future_base_time().

Very small period values may become zero after the conversion,
which can lead to a division by zero in future_base_time().

Round zero pin_duration up to 1 tick so that the smallest unsupported
periods use the minimum non-zero hardware duration instead of passing
zero to future_base_time().

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


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

Apply the vendor's patch.

## Is CVE-2026-72414 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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