Skip to main content
Audit date: 2026-11-10 (UTC)
Host: WSL2 on Windows
Distribution: Ubuntu 24.04.4 LTS
Kernel: 6.6.87.2-microsoft-standard-WSL2 (x86_64)
This page records observed results. Capabilities that could not be exercised without root are marked BLOCKED, not PASS.

Environment

Unprivileged audit:
Representative output:
A BLOCKED result from the unprivileged audit is the correct result. It is not evidence that kernel capture is broken.

Capability matrix

Privileged validation

Validated with an operator-authenticated sudo session on 2026-11-10.
  • sudo scripts/e2e-root.sh returned E2E PASS.
  • All seven tracepoints attached.
  • The lifecycle session completed and remained inspectable as the invoking user.
  • SIGINT exited 130 and finalized the session as interrupted.
  • The database was owned by the invoking user with mode 600.
  • Phase 5 run one: 72 events, including 64 file opens and one IPv4 connect.
  • Phase 5 run two: 315 events, including IPv4 127.0.0.1:1 and IPv6 ::1:1.
  • Both sessions verified valid with zero findings.
  • /etc/hostname opened successfully.
  • ringbuf_lost was zero in the validated sessions.
Two defects were found and fixed during validation:
  • Collector /proc enrichment generated recursive openat events. Self-originated samples are now filtered before enrichment.
  • The session lock directory was created as root before the privilege drop, causing the writer to fail. The lock is now acquired after the drop and is user-owned.

Reproduce the validation

Phase 5 manual capture:
If no activity rows appear, capture the exact error and treat live capture as unproven.

WSL2 notes

  • WSL2 exposes a real Linux kernel and real tracepoints. This is not emulated eBPF.
  • unprivileged_bpf_disabled=2 is host hardening, not a SYSCALL defect.
  • Tracefs being root-only is normal. Use sudo or scoped capabilities.
  • Do not weaken unprivileged_bpf_disabled or tracefs permissions to make a test pass.
  • If attach fails after a successful load, preserve the exact libbpf error.
  • The Phase 5 syscall tracepoints exist in the 6.6 WSL2 ABI and attached under root.
  • WSL2 localhost networking may refuse an unused port. A refused connect is still valid evidence.
  • If the workbench window is blank under WSLg:
WSLg used software compositing during validation; GPU acceleration and accessibility-bus integration were unavailable.

What remains unproven

  • A native Linux host run, beyond WSL2.
  • Stress and sustained-loss behavior.
  • Crash injection leaving a permanent recording session.
  • A privileged CI lane with explicit provisioning.
See Testing and Roadmap.