CVE-2026-90284

CVE CVE-2026-90284EUVD EUVD-2026-81877Published 2026-09-17T16:08:13.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.3-rc1; patch: 5.15.221; patch: 6.1.188; 5.14; ecb739cf15a9bae040ce6b60209b78b92512d120 <c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7; 4.19.203 <4.20; patch: 7.2.6; patch: 6.6.157; d09639528b66b5c7c20dc8f7fb8928aacabd40bb; 75d95e2e39b27f733f21e6668af1c9893a97de5e <fb4824880b0dba0e7b3a497c46c642f979630392; patch: 6.18.52; 75d95e2e39b27f733f21e6668af1c9893a97de5e <ea33fac0df7fe7b49a4b27acb83e227b82317d1d; 75d95e2e39b27f733f21e6668af1c9893a97de5e <5a250bff75a446374c05622973b18b4ab662b504; 75d95e2e39b27f733f21e6668af1c9893a97de5e <6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7b; patch: 0; 5.4.140 <5.5; c14a54675db7131791402fa22fb0fa6da1f5fb66; 75d95e2e39b27f733f21e6668af1c9893a97de5e <85aeb8fc61839098ae0942ccba86e669c08e75d4; 5.10.58 <5.10.270; 75d95e2e39b27f733f21e6668af1c9893a97de5e <93a2385730540105df8524447dcc11309ad280f9; 67cf0fbcac0d42d4d4686cddc1e39f465bbfec37; patch: 5.10.270; 5.13.10 <5.14; 75d95e2e39b27f733f21e6668af1c9893a97de5e <b48373c901951fad1a26bd7c33ad91172b3945b5; patch: 6.12.110

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.