DF-4960

led_set() always returns 0, swallowing ENOMEM/ENOENT from its own logic (DragonFly divergence)

Summary

DFly returns constant 0 where FreeBSD returns error - callers of the exported API cannot detect failures. Latent (no in-tree callers). return (error) fix.

Discussion (0)

No comments yet.

Severity: Info
Status: new
Bucket: Base system — drivers
Confidence: certain
Pass: 2 · GLM 5.3 second pass
CVSS 3.1: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:N
CWE: CWE-670
File: sys/dev/misc/led/led.c
Lines: 273-277
Area: dev
Discovered: 2026-09-25
Updated: 2026-09-25

Team triage

untriaged

priority: — · owner: —

PoC verification

untested

Status: untested
Reproduced: no
Impact: none
Confidence: certain
Tested: 2026-09-25 11:00:24
Attempts: 0
Runtime: —
Code hash: —
Guest: —
Build cmd: —
Run cmd: —

jump to evidence pack ↓

Fix verification

not_testable

Fix status: not_testable
Baseline reproduced: —
Patched reproduced: —
Confidence: certain
Tested: 2026-09-25 11:00:24
Runtime: —
Kernel: per-fix-DF-4960
fix.diff: findings/poc/DF-4960/fix.diff
Runner: df-bsd-reviewer

jump to fix verification ↓

PoC verification

Evidence pack

findings/poc/DF-4960 · 1 files

File	Type	Description	Size
verdict.json	file		586 B	view raw

Fix verification

not_testable

per-fix-DF-4960

Confirmed kernel references

sys/dev/misc/led/led.c:273-277

Detail

Exploit chain

none - latent API bug

Evidence (decisive lines)

findings/poc/DF-4960/ (this verdict)

Verdict

API-correctness (Info; DFly divergence): led_set computes error from led_parse (ENOMEM) and the name lookup (ENOENT) but returns constant 0 at :277 - FreeBSD returns error. Callers of the exported kernel API cannot detect a failed set. No in-tree callers today (latent). return (error) fix.