xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...) in a tempora…
xen
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
| No fix yet |
| Xen xen |
|
|
| Xen xen |
| No fix yet |
| Xen xen |
|
xen
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
| No fix yet |
| Xen xen |
|
|
| Xen xen |
| No fix yet |
| Xen xen |
|
| No fix yet |
xen/arm: Boot modules are not scrubbed The bootloader will load boot modules (e.g. kernel, initramfs...) in a temporary area before they are copied by Xen to each domain memory. To ensure sensitive data is not leaked from the modules, Xen must "scrub" them before handing the page over to the allocator. Unfortunately, it was discovered that modules will not be scrubbed on Arm.
From the CVE record · XEN
On Arm, Xen does not scrub boot modules before returning their pages to the allocator. This could expose sensitive module data if those pages are reused. The input does not specify attacker access, authentication, or user-interaction requirements.
Operators running Xen on Arm should check their installations; affected versions are not specified.