Security support

Canonical provides security maintenance for Zephyr 26.10. This page describes the security policy for every active release line. Specifically, What the policy encompasses, for how long, what Canonical fixes, how fixes reach you, and how to report a vulnerability.

Support period

Every active release line receives security fixes until its end of life. Within a release line, only the latest update receives security fixes. For the support level and end of life of each release line, see the Releases page.

Standard security maintenance lasts nine months. To keep receiving security fixes after that, please move to a newer release.

When the applicable maintenance period ends, Zephyr 26.10 will no longer receives security fixes.

What Canonical fixes

In line with Canonical’s Secure Software Development Lifecycle (SSDLC), Canonical fixes at least the following vulnerabilities in supported releases:

  • Every vulnerability rated High or Critical, with a CVSS 3.1 or 4.0 score of 7.0 or higher.

  • Every vulnerability in the CISA Known Exploited Vulnerabilities catalog, whatever its CVSS score.

Canonical fixes lower-severity vulnerabilities on a best-effort basis, usually as part of a routine update. All releases are validated on the supported platform set.

How fixes reach you

Canonical delivers security fixes as new updates of the 26.10 release series. Each update has a new immutable source tag. You receive the fixes when you move your workspace to the new tag and rebuild your firmware.

Canonical announces each update in:

See How to get security updates.

Report a vulnerability

If the upstream Zephyr Project still maintains the Zephyr version that your release line is based on, report the vulnerability upstream, as described in the upstream vulnerability reporting process. The Releases page lists the upstream end of life of each release line.

If upstream no longer maintains that version, report the vulnerability to Canonical as a Private Security bug in the Zephyr RTOS Launchpad bug tracker. Only the project’s security group can see Private Security bugs. Include a description of the problem, the steps to reproduce it, the affected versions, and any mitigations that you know of. You do not need a complete analysis or a proof of concept. If you are not sure whether a problem affects security, report it anyway.

Please do not report security problems in a public forum, such as a public Launchpad bug or a public GitHub repository, and do not disclose them publicly until Canonical has investigated them and coordinated a fix.

For how to collect the details of a report, see How to report a security vulnerability.

Disclosure

Zephyr 26.10 adopts the Ubuntu security disclosure and embargo policy, which describes what you can expect when you report a vulnerability and what Canonical expects from you. Canonical follows a coordinated disclosure process: it publishes the details of a vulnerability after a fix is available and any embargo has ended. Upstream Zephyr embargoes last at most 90 days.

See also

How-to guides:

Reference: