How to report a security vulnerability

Report security problems in Zephyr 26.10 privately, so that the maintainers can fix them before attackers learn about them. 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.

Prerequisites

Before starting, ensure you have these requirements satisfied:

  • The Zephyr 26.10 workspace where you found the problem.

  • A Launchpad account, if you report the problem to Canonical.

  • A GitHub account or an email client, if you report the problem upstream.

Collect the details

Run these commands from the root of your workspace.

Record the source tag:

$ git -C zephyr-manifest describe --tags --exact-match

Record the Zephyr repository revision:

$ git -C zephyr rev-parse HEAD

Also note:

  • The board name and board revision.

  • The steps to reproduce the problem.

  • The impact, if you know it.

  • Any mitigations that you have found.

Send the report

Zephyr 26.10 is based on upstream Zephyr 4.5. Where you send the report depends on whether the upstream Zephyr Project still maintains that version. The Releases page lists its upstream end of life.

If upstream still maintains Zephyr 4.5, report the problem upstream, as described in the upstream vulnerability reporting process. Open a draft security advisory on the Zephyr security advisories page, or email the details to vulnerabilities@zephyrproject.org.

If upstream no longer maintains Zephyr 4.5, report the problem to Canonical as a Private Security bug in Launchpad. Only the project’s security group can see Private Security bugs.

  1. In the Zephyr RTOS Launchpad bug tracker, select Report a bug.

  2. Enter a one-line summary of the problem. If Launchpad lists similar bugs, select No, I need to report a new bug.

  3. Describe the problem with the details that you collected.

  4. Select This bug is a security vulnerability. Launchpad files the bug as Private Security. If you are a bug supervisor for the project, Launchpad asks what information the bug contains instead: select Private Security.

  5. Select Submit Bug Report.

Do not report the problem in a public bug, pull request, or discussion, and do not disclose it publicly until the team that you reported it to has investigated it and coordinated a fix.

After you report

If you reported the problem upstream, the upstream Zephyr Project handles it as described in its vulnerability reporting process.

If you reported the problem to Canonical, Canonical handles the report under the Ubuntu security disclosure and embargo policy, which describes what to expect. Canonical publishes the details of a vulnerability after a fix is available and any embargo has ended. Canonical’s and Upstream’s embargoes last at most 90 days.

See also

Explanation:

How-to guides:

Reference: