Roadmaps / Embedded Linux / Phase 4
Phase 4 of 4 · Study weeks 13-16
Ship it: SBOM, vulnerabilities and the support promise
This phase turns an image into a product you can support for ten years and report on. Read the Yocto Project security manual on vulnerabilities, the sbom-cve-check documentation, and the European Commission's pages on the Cyber Resilience Act.
Topics every week
- Week 138 h
- SBOMs: what SPDX 3 holds and does not
- the SBOM Yocto generates
- licences in the image
Hand inThe image's SBOM and a list of packages by licence, with anything you cannot ship
- Week 148 h
- CVEs in Yocto 6.0:
sbom-cve-check(it replacedcve-check), statuses and reasons, kernel CVEs in bulk (the kernel reports very many; triage by policy), a triage policy
Hand inA CVE report: every open item in
gwd's closure has a status, reason and owner; kernel CVEs counted by status under a written policy - CVEs in Yocto 6.0:
- Week 158 h
- The support promise: Cyber Resilience Act timeline, vulnerability reporting, support period, key and certificate lifecycle, staged rollout
Hand inA readiness document (what the regulation asks, what your product does, the gaps) and a ten-year support timeline against Yocto 6.0 (to April 2030) and linux-yocto 6.18 (to Dec 2028)
- Week 168 h
- The drill: a seeded vulnerable library, rebuild, signed bundle, staged rollout to five instances, a halted rollout, an advisory
Hand inCheckpoint 4, built in four steps: the report; the patch and bundle; the rollout with a failing unit; the advisory and timeline (then the captures)
Practice projects
- Enable the CVE check in your build. Done when the report lists at least one open CVE with a status you chose and a reason a reviewer would accept.
- Write the staged rollout controller: one unit, then two, then all five, stopping when a unit fails its health check. Done when a seeded failing unit halts it and the others stay on the old image.
- (Optional for a fresher) Compare the SBOM with
dpkg-style package listings of a Debian image. Done when you can say which of the two shows build-time components and which does not.
GitHub repos to study
| Repo | What to read | Week |
|---|---|---|
| bootlin/sbom-cve-check | The tool's documentation and how it reads an SPDX file and treats statuses | 14 |
| openembedded/meta-openembedded | How recipes carry CVE status and patches | 14 |
| rauc/meta-rauc | The bundle recipe you will rebuild for the patch | 16 |
Milestone checkpoint
Run the drill and write the advisory. Done when the Checkpoint 4 row passes. Evidence: the SBOM, the CVE report with every status and reason, the policy, the rollout log with the halted unit, the advisory and the timeline against the 24-hour, 72-hour and 14-day marks, the readiness document, the ten-year support timeline, ADR-5 (CVE and triage policy: what you triage by hand and what by rule), and ADR-6 and ADR-7 for Senior.
Check yourself
Answer each question in your head first, then open it to check.
What does an SBOM tell you, and what can it not tell you?
It lists the components and versions in the image; it does not show whether a vulnerable function is reachable, or how a component is configured.Why can a CVE report list a vulnerability that does not affect you?
Matching is by component name and version, so a CVE can name code you did not build or a configuration you do not use; the status and reason record that decision.What must a staged rollout stop on?
A health-check failure rate above a threshold you set before the rollout, not a human noticing.What does the Cyber Resilience Act ask of a manufacturer when a vulnerability is exploited?
Reporting an actively exploited vulnerability: an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within 14 days after a corrective measure is available (the 14 days do not run from awareness). Reports go through the ENISA Single Reporting Platform, which sends them to the national CSIRT. Severe incidents have the same first two steps and a final report within one month of the notification. The product class and conformity route (self-assessment or a notified body) depend on the product: ask your legal contact. Manufacturers' main obligations apply from 11 Dec 2027 (secondary sources; confirm on eur-lex). Check the Commission's page for the dates in force.How would you prove to an auditor that you shipped a fix?
The signed bundle, the rebuilt SBOM showing the fixed version, the rollout log and the advisory with dates.