fix: mbz check range for sev-snp report parsing

[sachaservan]

Summary by cubic

Fixes SEV-SNP report parsing by making the MBZ range version-aware. v5+ skips launch_mit_vector and current_mit_vector, while v2/v3 still enforce MBZ from 0x1F8, so valid v5+ reports are accepted.

• Bug Fixes
  • Set MBZ start to 0x1F8 for versions <5 and 0x208 for v5+, checking only reserved bytes before the signature.
  • Added inline comments documenting v5+ field layout and the reserved range.

^{Written for commit 4303518. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/tinfoil/attestation/abi_sev.py">

<violation number="1" location="src/tinfoil/attestation/abi_sev.py:330">
P2: Make this MBZ range version-aware. The new unconditional `0x208` start skips reserved-byte validation for v2/v3 reports.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}