ieee802154: ca8210: fix cas_ctl leak on spi_async failure
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.22% (FIRST EPSS).
- Fixed version: Linux Linux 460c5cd51e4d7d15b317f178f42cfcb666c0fe91, 7e3630fbb6aabb844bbf35746dee0bf3894100c7, b07aea90dbc6e188c74c100af64b77b9482ffc65.
Low priority for now. Upgrade to Linux Linux 460c5cd51e4d7d15b317f178f42cfcb666c0fe91, 7e3630fbb6aabb844bbf35746dee0bf3894100c7, b07aea90dbc6e188c74c100af64b77b9482ffc65 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
In the Linux kernel, the following vulnerability has been resolved: ieee802154: ca8210: fix cas_ctl leak on spi_async failure ca8210_spi_transfer() allocates cas_ctl with kzalloc_obj(GFP_ATOMIC) and relies entirely on the SPI completion callback ca8210_spi_transfer_complete() to free it. The spi_async() API only invokes the completion callback on successful submission. On failure it returns a negative error code without ever queuing the callback, which leaves cas_ctl and its embedded spi_message and spi_transfer orphaned. Every kfree(cas_ctl) in the driver is inside the completion callback, so there is no other reclamation path. ca8210_spi_transfer() is called from ca8210_spi_exchange(), the interrupt handler ca8210_interrupt_handler(), and from the retry path inside the completion callback itself. The exchange and interrupt handler paths loop on -EBUSY, so under sustained SPI bus contention every retry iteration leaks a fresh cas_ctl (~600 bytes per occurrence). Fix it by freeing cas_ctl on the spi_async() error path. While here, correct the misleading error string: the function calls spi_async(), not spi_sync().
- Published
- Aug 15, 2026
- Updated
- Aug 17, 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
- 4.12affected
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before 460c5cd51e4d7d15b317f178f42cfcb666c0fe91affected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before b07aea90dbc6e188c74c100af64b77b9482ffc65affected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before fe90605b651573d30be8293ff5be40e3d7023117affected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before b9071dc7889bef42590e04fbf3e56cc65e1e5e6eaffected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before d4a397fe803c2d157f6ebb068b802ef75fbf109eaffected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before cb5cca1d2a908ddd5e357971de0f2009617b8d6aaffected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before 7e3630fbb6aabb844bbf35746dee0bf3894100c7affected · git
- ded845a781a578dfb0b5b2c138e5a067aa3b1242 and later · before e09390e439bd7cca30dd10893b1f64802961667aaffected · git
- before 4.12not 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 460c5cd51e4d7d15b317f178f42cfcb666c0fe91 | Vendor (CNA) |
| Linux Linux | 7e3630fbb6aabb844bbf35746dee0bf3894100c7 | Vendor (CNA) |
| Linux Linux | b07aea90dbc6e188c74c100af64b77b9482ffc65 | Vendor (CNA) |
| Linux Linux | b9071dc7889bef42590e04fbf3e56cc65e1e5e6e | Vendor (CNA) |
| Linux Linux | cb5cca1d2a908ddd5e357971de0f2009617b8d6a | Vendor (CNA) |
| Linux Linux | d4a397fe803c2d157f6ebb068b802ef75fbf109e | Vendor (CNA) |
| Linux Linux | e09390e439bd7cca30dd10893b1f64802961667a | Vendor (CNA) |
| Linux Linux | fe90605b651573d30be8293ff5be40e3d7023117 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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/7e3630fbb6aabb844bbf35746dee0bf3894100c7
- git.kernel.org/stable/c/b07aea90dbc6e188c74c100af64b77b9482ffc65
- git.kernel.org/stable/c/b9071dc7889bef42590e04fbf3e56cc65e1e5e6e
- git.kernel.org/stable/c/cb5cca1d2a908ddd5e357971de0f2009617b8d6a
- git.kernel.org/stable/c/d4a397fe803c2d157f6ebb068b802ef75fbf109e
- git.kernel.org/stable/c/e09390e439bd7cca30dd10893b1f64802961667a
- git.kernel.org/stable/c/fe90605b651573d30be8293ff5be40e3d7023117
Vendor advisories and official records. Exploit/PoC links are deliberately left out.