CVE-2026-90284

firmware_loader: do not queue completed sysfs fallback requests

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: firmware_loader: do not queue completed sysfs fallback requests fw_load_sysfs_fallback() calls device_add() before adding the fw_priv to pending_fw_head. device_add() publishes the fallback loading interface, so a userspace helper which discovers the device by scanning sysfs can write 0 to the loading attribute and complete the request before it is queued as pending. In that interleaving firmware_loading_store() calls fw_state_done() while pending_list still points to itself, so it cannot remove an entry from pending_fw_head. The subsequent unconditional list_add() then queues an already-completed fw_priv. Once the request is released, pending_fw_head can retain a pointer to freed memory and the next fallback request can fault while validating the list. Only in-flight fallback requests need suspend or reboot abort handling. If the request is already DONE after device_add(), return success from the fallback path without sending another uevent, waiting again, or queueing it as pending. This preserves the invariant that pending_fw_head contains only active fallback requests.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.2035.10.585.13.105.145.4.14067cf0fbcac0d42d4d4686cddc1e39f465bbfec3775d95e2e39b27f733f21e6668af1c9893a97de5ec14a54675db7131791402fa22fb0fa6da1f5fb66d09639528b66b5c7c20dc8f7fb8928aacabd40bbecb739cf15a9bae040ce6b60209b78b92512d120
Vendor states this is fixed in 5a250bff75a446374c05622973b18b4ab662b504 (fixed)
Vendor states this is fixed in 6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7b (fixed)
Vendor states this is fixed in 85aeb8fc61839098ae0942ccba86e669c08e75d4 (fixed)
Vendor states this is fixed in 93a2385730540105df8524447dcc11309ad280f9 (fixed)
Vendor states this is fixed in b48373c901951fad1a26bd7c33ad91172b3945b5 (fixed)
Vendor states this is fixed in c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7 (fixed)
Vendor states this is fixed in ea33fac0df7fe7b49a4b27acb83e227b82317d1d (fixed)
Vendor states this is fixed in fb4824880b0dba0e7b3a497c46c642f979630392 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card