Menu

Star on GitHub · 3.2k

CVE-2026-72414

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 ti…

Published Aug 15, 2026EPSS 0.22%

Overview

CVE-2026-72414 is a known-severity vulnerability. It was published on August 15, 2026.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72414?

CVE-2026-72414 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72414?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72414?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72414?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72414 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.