CVE-2026-90284 — firmware_loader: do not queue completed sysfs fallback requests
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ecb739cf15a9bae040ce6b60209b78b92512d120 and < c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < 93a2385730540105df8524447dcc11309ad280f9≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < ea33fac0df7fe7b49a4b27acb83e227b82317d1d≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < 5a250bff75a446374c05622973b18b4ab662b504≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < 85aeb8fc61839098ae0942ccba86e669c08e75d4≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < 6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7b≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < fb4824880b0dba0e7b3a497c46c642f979630392≥ 75d95e2e39b27f733f21e6668af1c9893a97de5e and < b48373c901951fad1a26bd7c33ad91172b3945b5 and 8 moreversion 67cf0fbcac0d42d4d4686cddc1e39f465bbfec37version d09639528b66b5c7c20dc8f7fb8928aacabd40bbversion c14a54675db7131791402fa22fb0fa6da1f5fb66≥ 5.10.58 and < 5.10.270≥ 4.19.203 and < 4.20≥ 5.4.140 and < 5.5≥ 5.13.10 and < 5.14version 5.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- nvd.nist.gov/vuln/detail/CVE-2026-90284
- git.kernel.org/stable/c/85aeb8fc61839098ae0942ccba86e669c08e75d4
- github.com/advisories/GHSA-97xh-425q-x269
- git.kernel.org/stable/c/b48373c901951fad1a26bd7c33ad91172b3945b5
- git.kernel.org/stable/c/fb4824880b0dba0e7b3a497c46c642f979630392
- git.kernel.org/stable/c/6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7b
- git.kernel.org/stable/c/5a250bff75a446374c05622973b18b4ab662b504
- git.kernel.org/stable/c/ea33fac0df7fe7b49a4b27acb83e227b82317d1d
- git.kernel.org/stable/c/93a2385730540105df8524447dcc11309ad280f9
- git.kernel.org/stable/c/c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98860 HID: bpf: cast size to ssize_t when checking hid_bpf_hw_request 1d
- Unknown CVE-2026-98865 sched_ext: Don't run ops.dequeue() with a DSQ lock held 1d
- Unknown CVE-2026-98864 sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90284 is "firmware_loader: do not queue completed sysfs fallback requests", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.