You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
components: standardise the hardware: meta field on the requirement
The hardware: key is defined as the hardware requirement, but several
components put a mitigation there -- prefetch and prefetch_directmap named
"KPTI", sidt named "UMIP", which read as "requires KPTI/UMIP" when the leak
in fact needs them absent. Name the requirement and move the mitigating
feature into a trailing "(mitigated by X)", matching databounce's form:
prefetch, prefetch_directmap: prefetch side-channel (mitigated by KPTI)
sidt: user-mode SIDT (mitigated by UMIP)
Spell out the convention in the KASLD_META doc and the hardening-render
comment, and add a check-component-meta rule that fails a bare KPTI/UMIP
left where the requirement goes (KPTI is a kernel config, not hardware;
UMIP is a CPU feature that only ever blocks user-mode leaks).
0 commit comments