CVE-2026-72048 — ieee802154: ca8210: fix cas_ctl leak on spi_async failure
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().
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 |
≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < 460c5cd51e4d7d15b317f178f42cfcb666c0fe91≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < b07aea90dbc6e188c74c100af64b77b9482ffc65≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < fe90605b651573d30be8293ff5be40e3d7023117≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < b9071dc7889bef42590e04fbf3e56cc65e1e5e6e≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < d4a397fe803c2d157f6ebb068b802ef75fbf109e≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < cb5cca1d2a908ddd5e357971de0f2009617b8d6a≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < 7e3630fbb6aabb844bbf35746dee0bf3894100c7≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 and < e09390e439bd7cca30dd10893b1f64802961667a and 1 moreversion 4.12 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
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× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/7e3630fbb6aabb844bbf35746dee0bf3894100c7
- git.kernel.org/stable/c/e09390e439bd7cca30dd10893b1f64802961667a
- git.kernel.org/stable/c/b9071dc7889bef42590e04fbf3e56cc65e1e5e6e
- git.kernel.org/stable/c/460c5cd51e4d7d15b317f178f42cfcb666c0fe91
- git.kernel.org/stable/c/b07aea90dbc6e188c74c100af64b77b9482ffc65
- git.kernel.org/stable/c/d4a397fe803c2d157f6ebb068b802ef75fbf109e
- git.kernel.org/stable/c/cb5cca1d2a908ddd5e357971de0f2009617b8d6a
- git.kernel.org/stable/c/fe90605b651573d30be8293ff5be40e3d7023117
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
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-72048 is "ieee802154: ca8210: fix cas_ctl leak on spi_async failure", 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.22% 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.