DF-0313
Sticky Hop-by-Hop/Destination options un-settable: hardcoded priv=0 always returns EPERM for root
Summary
ip6_pcbopt(:2019) hardcodes priv=0. IPV6_HOPOPTS/DSTOPTS in ip6_setpktoption check if(!priv)return(EPERM). Root can NEVER set sticky ext headers via setsockopt. RFC 3542 non-conformance. Overly restrictive not bypass. Sendmsg cmsg path unaffected.
Discussion (0)
PoC verification
Evidence pack
findings/poc/DF-0313 Β· 1 files| File | Type | Description | Size | |
|---|---|---|---|---|
| manifest.json | file | 392 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/netinet6/ip6_output.c:2019: sticky HBH/Dst options un-settable (hardcoded priv=0)
Verified recommended fix
Source-confirmed at sys/netinet6/ip6_output.c:2019: sticky HBH/Dst options un-settable (hardcoded priv=0)
Verdict
Source-confirmed at sys/netinet6/ip6_output.c:2019: sticky HBH/Dst options un-settable (hardcoded priv=0)
No comments yet.