CVE-2026-90284: firmware_loader: do not queue completed sysfs fallback requests
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 4.20, 5.10.270, 5.14; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 4.20, 5.10.270, 5.14; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 67cf0fbcac0d42d4d4686cddc1e39f465bbfec37, d09639528b66b5c7c20dc8f7fb8928aacabd40bb, c14a54675db7131791402fa22fb0fa6da1f5fb66, 5.14affected
- ecb739cf15a9bae040ce6b60209b78b92512d120 and later · before c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7affected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before 93a2385730540105df8524447dcc11309ad280f9affected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before ea33fac0df7fe7b49a4b27acb83e227b82317d1daffected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before 5a250bff75a446374c05622973b18b4ab662b504affected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before 85aeb8fc61839098ae0942ccba86e669c08e75d4affected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before 6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7baffected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before fb4824880b0dba0e7b3a497c46c642f979630392affected · git
- 75d95e2e39b27f733f21e6668af1c9893a97de5e and later · before b48373c901951fad1a26bd7c33ad91172b3945b5affected · git
- 5.10.58 and later · before 5.10.270affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90282Sep 17, 2026 · phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend0Monitor
- ← EarlierCVE-2026-90283Sep 17, 2026 · hugetlbfs: release subpool on fill_super failure0Monitor
- Later →CVE-2026-90285Sep 17, 2026 · scsi: qla2xxx: Remove redundant VPD flash read in sysfs read path0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.10.270 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5a250bff75a446374c05622973b18b4ab662b504 | Vendor (CNA) |
| Linux Linux | 6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7b | Vendor (CNA) |
| Linux Linux | 85aeb8fc61839098ae0942ccba86e669c08e75d4 | Vendor (CNA) |
| Linux Linux | 93a2385730540105df8524447dcc11309ad280f9 | Vendor (CNA) |
| Linux Linux | b48373c901951fad1a26bd7c33ad91172b3945b5 | Vendor (CNA) |
| Linux Linux | c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7 | Vendor (CNA) |
| Linux Linux | ea33fac0df7fe7b49a4b27acb83e227b82317d1d | Vendor (CNA) |
| Linux Linux | fb4824880b0dba0e7b3a497c46c642f979630392 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6eaa632d0ed7bbb84f9cb670e5ec4e2cecf4cc7b
- git.kernel.org/stable/c/85aeb8fc61839098ae0942ccba86e669c08e75d4
- git.kernel.org/stable/c/93a2385730540105df8524447dcc11309ad280f9
- git.kernel.org/stable/c/b48373c901951fad1a26bd7c33ad91172b3945b5
- git.kernel.org/stable/c/c8b97c5130f27b64fa2cfe1aa4bebb13f724c6c7
- git.kernel.org/stable/c/ea33fac0df7fe7b49a4b27acb83e227b82317d1d
- git.kernel.org/stable/c/fb4824880b0dba0e7b3a497c46c642f979630392
Vendor advisories and official records. Exploit/PoC links are deliberately left out.