DF-0913
fuse_audit_length / fuse_get_ops panic kernel on unknown opcode
Summary
fuse_util.c:230 fuse_panic(Invalid opcode) in fuse_audit_length default. :334 fuse_panic in fuse_get_ops default. fuse_panic -> panic() (debug.h:41-42). Opcode from kernel request header not attacker-controlled today. But any new fuse_abi.h opcode not added to switch = instant kernel panic on next FUSE operation. Fragile defense-in-depth. Fix: return -1 / return FUSE_UNKNOWN.
Discussion (0)
PoC verification
Evidence pack
findings/poc/DF-0913 Β· 1 files| File | Type | Description | Size | |
|---|---|---|---|---|
| manifest.json | file | 389 B | view raw |
Fix verification
not_testablebaseline reproducedβ patch + rebuild βpatched clean
recommended fix identified; fix.diff not authored/validated in this batch
recommended fix identified; fix.diff not authored/validated in this batch
combined build rc=0
Confirmed kernel references
β
Detail
Exploit chain
none (Info severity)
Evidence (decisive lines)
Source-confirmed at sys/vfs/fuse/fuse_util.c:229: fuse_audit_length/fuse_get_ops panic kernel on unknown opcode
Verified recommended fix
Source-confirmed at sys/vfs/fuse/fuse_util.c:229: fuse_audit_length/fuse_get_ops panic kernel on unknown opcode
Verdict
Source-confirmed at sys/vfs/fuse/fuse_util.c:229: fuse_audit_length/fuse_get_ops panic kernel on unknown opcode
No comments yet.