CVE-2026-90410: spi: davinci: switch to managed controller allocation
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 1a7958ce58dc95b06615df00c120ece4eb9ccc86, 2382f18daa4303923d66526db984e9a38074a312, 29e37f768f35592e26477f703649bd2e6f18d857.
Low priority for now. Upgrade to Linux Linux 1a7958ce58dc95b06615df00c120ece4eb9ccc86, 2382f18daa4303923d66526db984e9a38074a312, 29e37f768f35592e26477f703649bd2e6f18d857 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: spi: davinci: switch to managed controller allocation The controller is allocated with the non-managed spi_alloc_host() while the interrupt is registered with devm_request_threaded_irq(). During removal, spi_bitbang_stop() only unregisters the controller; the subsequent spi_controller_put() then frees the controller together with its embedded davinci_spi devdata, which is the IRQ handler's dev_id. The devm_request_threaded_irq() release action (free_irq()), which drains the handler, does not run until after .remove() returns. A late or latched interrupt can therefore reach davinci_spi_irq() and dereference already-freed memory. Switch to devm_spi_alloc_host() so that the devres LIFO order releases the controller only after free_irq() has drained the handler, and drop the now-redundant spi_controller_put() from .remove(). The probe error path is simplified to direct returns. The clock is acquired with devm_clk_get_enabled(), which is registered after the IRQ and thus released before it by the devres LIFO order. Drain the interrupt explicitly with devm_free_irq() before disabling the controller so that a late interrupt cannot access the registers of a clock-gated controller. This issue was found by an in-house static analysis tool.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th 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
- 3.14affected
- 5b3bb5963ff23a344062aba04937533a6f575761 and later · before 2382f18daa4303923d66526db984e9a38074a312affected · git
- 5b3bb5963ff23a344062aba04937533a6f575761 and later · before 29e37f768f35592e26477f703649bd2e6f18d857affected · git
- 5b3bb5963ff23a344062aba04937533a6f575761 and later · before f9452eba71fbfcee55c0b8e030ee3615e9f75f65affected · git
- 5b3bb5963ff23a344062aba04937533a6f575761 and later · before 3b544072185c3d19ddec621ec9f6897ea2d10ee3affected · git
- 5b3bb5963ff23a344062aba04937533a6f575761 and later · before 1a7958ce58dc95b06615df00c120ece4eb9ccc86affected · git
- 5b3bb5963ff23a344062aba04937533a6f575761 and later · before ea408a05dc8f18b4a184b88d6e19d2fd1acc1527affected · git
- before 3.14not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · 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 | from 0 | — |
| 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-90408Sep 17, 2026 · wifi: ath12k: fix overreads in ath12k_wmi_process_csa_switch_count_event()30Monitor
- ← EarlierCVE-2026-90409Sep 17, 2026 · drm/panthor: Add vm_bind region with kbo range overlap check0Monitor
- Later →CVE-2026-90411Sep 17, 2026 · nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request0Monitor
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 | 1a7958ce58dc95b06615df00c120ece4eb9ccc86 | Vendor (CNA) |
| Linux Linux | 2382f18daa4303923d66526db984e9a38074a312 | Vendor (CNA) |
| Linux Linux | 29e37f768f35592e26477f703649bd2e6f18d857 | Vendor (CNA) |
| Linux Linux | 3b544072185c3d19ddec621ec9f6897ea2d10ee3 | Vendor (CNA) |
| Linux Linux | ea408a05dc8f18b4a184b88d6e19d2fd1acc1527 | Vendor (CNA) |
| Linux Linux | f9452eba71fbfcee55c0b8e030ee3615e9f75f65 | Vendor (CNA) |
| 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 (5 more)Show less
- git.kernel.org/stable/c/2382f18daa4303923d66526db984e9a38074a312
- git.kernel.org/stable/c/29e37f768f35592e26477f703649bd2e6f18d857
- git.kernel.org/stable/c/3b544072185c3d19ddec621ec9f6897ea2d10ee3
- git.kernel.org/stable/c/ea408a05dc8f18b4a184b88d6e19d2fd1acc1527
- git.kernel.org/stable/c/f9452eba71fbfcee55c0b8e030ee3615e9f75f65
Vendor advisories and official records. Exploit/PoC links are deliberately left out.