CVE-2026-89851: scsi: qla2xxx: Fix FCE trace enable parsing in debugfs
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix FCE trace enable parsing in debugfs
qla2x00dfsfcewrite() called kstrtoul() with a NULL result pointer, so a successful parse would dereference NULL and oops. Worse, the int return value (0 on success, negative errno on failure) was assigned to the unsigned long enable flag, inverting the intended logic: a valid number was treated as "disable" while a parse failure enabled FCE.
Parse the value into enable and propagate parse errors to userspace.
Affected Software
Event History
Frequently Asked Questions
Who can trigger the fault?
An attacker or user would need the ability to write to the qla2xxx FCE trace debugfs interface. The issue is in the debugfs write handler, so systems without access to that interface are not exposed through this path.
What happens when a valid value is written to the affected interface?
A successful parse dereferences a NULL pointer and can cause a kernel oops. Before the fix, valid numeric input was also interpreted as disabling FCE rather than enabling it.
Can invalid input have an unexpected effect?
Yes. Before the fix, a parse failure was assigned to the unsigned enable flag and resulted in FCE being enabled. The fix instead returns parsing errors to userspace.