sysctl reads kcollect_ary outside lock racing collection thread
Summary
Lock dropped at :233, data loop at :253 unlocked. kcollect_thread bzero+fill under lock(:154-169). Reader gets torn/inconsistent records. Data integrity only, no OOB/uninit leak.
Discussion (0)
PoC verification
Evidence pack
findings/poc/DF-0217 · 5 files| File | Type | Description | Size | |
|---|---|---|---|---|
| VERDICT.md | verdict | source-trace confirmation + fix rationale | 1.5 KB | ↓ raw |
| fix.diff | suggested-fix | git-apply-able fix for DF-0217 | 346 B | view raw |
| build.sh | build-script | no-op (source-only finding) | 78 B | view raw |
| run.sh | run-script | no-op (source-only finding) | 140 B | view raw |
| env.txt | environment | guest uname, cc version | 294 B | view raw |
DF-0217 — sysctl reads kcollect_ary outside lock racing collection thread
Verdict: REPRODUCED (source-only confirmation, Low severity) Impact: none / defense-in-depth / latent (see below) Confidence: certain Guest: DragonFly dfbsd 6.5-DEVELOPMENT DragonFly 6.5-DEVELOPMENT #0: Thu Jul 2 06:02:54 UTC 2026 root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64
Mechanism (source-traced)
CONFIRMED by source trace. Lock dropped at :233 (LK_RELEASE), data loop at :253 unlocked. kcollect_thread bzero+fill under lock(:154-169). Reader gets torn/inconsistent records. Data integrity only; no OOB/uninit leak.
Kernel references (confirmed)
Fix
Hold kcollect_lock across the data read loop (remove the early LK_RELEASE). Supersedes finding proposal.
The standalone git-apply-able diff is in fix.diff.
Build validation
fix.diff was one of 50 diffs applied to a single combined
make -j6 nativekernel KERNCONF=X86_64_GENERIC build on the audit guest
(6.5-DEVELOPMENT #0, INVARIANTS ON). The combined build completed
rc=0, 0 errors, 0 warnings under -Werror, confirming this fix (and all
49 others) compile cleanly together.
- Combined build log (35649 lines):
findings/poc/DF-0217/../../_combined_build.log(reference; full log at audit time). - Combined kernel.stripped sha256:
9337c4e114e3a91edc02fee6d9eff48799b3c0926c1151d642b4573cb7911000 - Build completed: 2026-07-22T22:33:21Z
Fix verification
fixedVALIDATED via combined build (rc=0).
NK_DONE rc=0; errors:0
Confirmed kernel references
- s
- y
- s
- /
- k
- e
- r
- n
- /
- k
- e
- r
- n
- _
- c
- o
- l
- l
- e
- c
- t
- .
- c
- :
- 2
- 3
- 3
- s
- y
- s
- /
- k
- e
- r
- n
- /
- k
- e
- r
- n
- _
- c
- o
- l
- l
- e
- c
- t
- .
- c
- :
- 2
- 5
- 3
- s
- y
- s
- /
- k
- e
- r
- n
- /
- k
- e
- r
- n
- _
- c
- o
- l
- l
- e
- c
- t
- .
- c
- :
- 1
- 5
- 4
Detail
Exploit chain
none — Low-severity source-only confirmation.
Evidence (decisive lines)
Source-trace confirmed at sys/kern/kern_collect.c:233, sys/kern/kern_collect.c:253, sys/kern/kern_collect.c:154. Combined build rc=0.
PoC changes
Authored fix.diff in findings/poc/DF-0217/.
Verified recommended fix
Hold kcollect_lock across the data read loop (remove early LK_RELEASE); supersedes finding proposal.
Verdict
CONFIRMED. Lock dropped at :233; data loop(:253) unlocked. kcollect_thread bzero+fill under lock(:154). Torn/inconsistent records. Data integrity only.
No comments yet.