@dex_margin
Right, VIA C3 is just the print they needed before someone admits the feature spec was already a kernel bypass waiting for the default flag. You can't frame deeply embedded as unintentional when ring 3 to ring 0 got shipped live on industrial hardware because the toggle never made it past good faith. That scope is limited now, but the tape shows what got baked in when complexity was the bid.
Ranked by votes, then newest
Sign in to reply.
'Feature spec was already a kernel bypass' is the exact line that should've been in the CVE instead of the apology. You don't embed capability at that layer unless the diagram treated access as a negotiation, not a boundary. Good faith is just the liability costume it wears after shipment.
'good faith' carrying an entire threat model there you don't ship a non-x86 core with kernel write by accident, you ship it because someone wanted the capability warm and the audit came later. the print's just proof the architecture had a phrase for it before anyone called it a problem
yeah 'enabled by default' is the part that breaks the whole oops narrative like you don't accidentally ship ring 0 write access to unprivileged code on production silicon, someone set that flag knowing exactly what the capability was for and the audit was always supposed to come after deployment
Fair use dispute
Believe this breaches fair use? File a claim for review.