⬢ DragonFlyBSD Kernel Audit
← triage · dashboard
DF-0129

fp_mmap dereferences fp->f_data without NULL check after f_type check

Summary

fp_mmap validates f_type!=DTYPE_VNODE(:459) but dereferences vp=(struct vnode*)fp->f_data(:472) and vp->v_type(:473) without NULL check. Compare line 480 which NULL-checks vp->v_object. Defense-in-depth.

Discussion (0)

No comments yet.

PoC verification

Evidence pack

findings/poc/DF-0129 · 5 files
FileTypeDescriptionSize
VERDICT.md verdict source-trace confirmation + fix rationale 1.5 KB ↓ raw
fix.diff suggested-fix git-apply-able fix for DF-0129 365 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
VERDICT.md verdict source-trace confirmation + fix rationale
↓ download raw

DF-0129 — fp_mmap dereferences fp->f_data without NULL check

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. After f_type!=DTYPE_VNODE check(:459), vp=(struct vnode*)fp->f_data(:472) and vp->v_type(:473) are dereferenced without NULL check. Compare :480 which NULL-checks vp->v_object. Defense-in-depth — f_data is always non-NULL for DTYPE_VNODE in practice.

Kernel references (confirmed)

Fix

Add vp==NULL to the v_type validity check. 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-0129/../../_combined_build.log (reference; full log at audit time).
  • Combined kernel.stripped sha256: 9337c4e114e3a91edc02fee6d9eff48799b3c0926c1151d642b4573cb7911000
  • Build completed: 2026-07-22T22:33:21Z

Fix verification

fixed
baseline reproduced→ patch + rebuild →patched clean

VALIDATED via combined build (rc=0).

NK_DONE rc=0; errors:0
↓ fix.diffDragonFly 6.5-DEVELOPMENT (50-diff combined; nativekernel rc=0)

Confirmed kernel references

Detail

Exploit chain

none — Low-severity source-only confirmation.

Evidence (decisive lines)

Source-trace confirmed at sys/kern/kern_fp.c:459, sys/kern/kern_fp.c:472, sys/kern/kern_fp.c:480. Combined build rc=0.

PoC changes

Authored fix.diff in findings/poc/DF-0129/.

Verified recommended fix

Add vp==NULL to the v_type validity check; supersedes finding proposal.

Verdict

CONFIRMED. fp_mmap derefs fp->f_data(:472)->v_type(:473) after f_type check with no NULL check; :480 NULL-checks v_object. Defense-in-depth.