systemd-boot loads unverified device tree blobs under Secure Boot
Key facts
- Attack vector
- Physical
- Privileges required
- High
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-6m6p-rjcq-334c. Fix status from GitHub.
Summary
systemd 250 and later on arm64 and riscv64 is affected. systemd-boot loads a device tree blob that a local user specifies, even when Secure Boot is enabled in type #1 BLS setups. A local attacker with high privileges needs a user to interact, and the impact is low because the source reports no Shim-trusted arm64 or riscv64 systemd-boot binaries are published.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact On arm64 and riscv64, systemd-boot allows a local user to specify a device tree blob and loads it, even when secure boot mode is enabled when using `type #1` BLS setups. DTBs are loaded and parsed by the kernel before ExitBootServices(), and the kernel itself disallows loading DTBs via the `dtb=` kernel command line option when secure boot is enabled. This feature was introduced in v250 by: https://github.com/systemd/systemd/commit/6e86342bb82 As far as we are aware, there are no Shim-trusted arm64/riscv64 systemd-boot binaries published anywhere, so the severity and impact are low, as it affects only local self-signed secure boot deployments of systemd-boot on arm64/riscv64. ### Patches Fixed in main and 254.4 253.11 252.17 251.19 250.13 https://github.com/systemd/systemd/pull/29228 https://github.com/systemd/systemd-stable/pull/324 https://github.com/systemd/systemd-stable/pull/325 https://github.com/systemd/systemd-stable/pull/326 https://github.com/systemd/systemd-stable/pull/327 https://github.com/systemd/systemd-stable/pull/328 ### Workarounds Use `type #2` BLS setups ### References https://github.com/systemd/systemd/pull/29228
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | systemd | >= 250 | 255 254.4 253.11 252.17 251.19 250.13 | Patch available | GHSA-6m6p-rjcq-334c |
- systemd Vendor— Affected >= 250 Fixed in 255 254.4 253.11 252.17 251.19 250.13 Patch available GHSA-6m6p-rjcq-334c
Remediation
Upgrade systemd to 255, 254.4, 253.11, 252.17, 251.19 or 250.13, matching your release branch. Use type #2 BLS setups as a workaround.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-6m6p-rjcq-334c systemd Fixed in 255 254.4 253.11 252.17 251.19 250.13 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-6m6p-rjcq-334c
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences