#1782·lynis

[STRG-1846] False positive: FireWire check flags systems with no 1394 hardware

Author: adjenkCreated Sep 14, 2026Updated Sep 14, 2026

Describe the bug Test STRG-1846 ("Disable drivers like firewire storage when not used") flags the system even when no FireWire hardware is present and no FireWire modules are loaded. The check only verifies that the kernel module file exists on disk and that no blacklist firewire-core line exists in /etc/modprobe.d/, without first checking whether a 1394 controller is actually present.

On a system with no FireWire port, the module will never load regardless of blacklisting, so the suggestion is meaningless.

Version

  • Distribution: Fedora 44
  • Lynis version: 3.1.7

Expected behavior The check should skip (or pass) when no 1394 controller is detected.

Output

  • Checking firewire ohci driver (modprobe config) [ NOT DISABLED ]
  • Disable drivers like firewire storage when not used, to prevent unauthorized storage or data theft [STRG-1846]

$ lsmod | grep firewire (no output)

$ lspci | grep -i "1394|firewire" (no output)

$ find /lib/modules/$(uname -r) -name "firewire" /lib/modules/7.2.5-200.fc44.x86_64/kernel/drivers/firewire /lib/modules/7.2.5-200.fc44.x86_64/kernel/drivers/firewire/firewire-core.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/drivers/firewire/firewire-net.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/drivers/firewire/firewire-ohci.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/drivers/firewire/firewire-sbp2.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/drivers/media/firewire /lib/modules/7.2.5-200.fc44.x86_64/kernel/sound/firewire /lib/modules/7.2.5-200.fc44.x86_64/kernel/sound/firewire/digi00x/snd-firewire-digi00x.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/sound/firewire/motu/snd-firewire-motu.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/sound/firewire/tascam/snd-firewire-tascam.ko.xz /lib/modules/7.2.5-200.fc44.x86_64/kernel/sound/firewire/snd-firewire-lib.ko.xz

Additional context The modules are shipped in the base kernel-core RPM but are never loaded without hardware. The check's current logic (module on disk + not blacklisted → warning) produces a false positive on any system without a 1394 controller. Suggested fix: add an early-exit when lspci shows no 1394 device.

Related: #270 (similar false positive reported for embedded systems in 2016, never resolved).