DF-5056
smu10_smu_init error paths leave hwmgr->smu_backend dangling after kfree(priv)
Summary
smu_backend is published before the two BO allocations; both error paths kfree(priv) without NULLing it (and mask the real error with -EINVAL). NOT reachable today (status.sw gates sw_fini dispatch) - latent lifetime trap for any future error-path unwind. Requires Raven silicon. NULL-out + propagate-real-error one-liner fix.
Discussion (0)
PoC verification
Evidence pack
findings/poc/DF-5056 Β· 1 files| File | Type | Description | Size | |
|---|---|---|---|---|
| verdict.json | file | 933 B | view raw |
Fix verification
not_testablebaseline noβ patch + rebuild βpatched clean
per-fix-DF-5056
Confirmed kernel references
Detail
Evidence (decisive lines)
source-level analysis in finding markdown
Verified recommended fix
hwmgr->smu_backend = NULL on both error paths; return r
Verdict
untested (hardware-gated: no AMD Raven on audit guest)
No comments yet.