In the Linux kernel, the following vulnerability has been resolved:
iio: mma8452: Fix trigger reference couting
The mma8452 driver directly assigns a trigger to the struct iio_dev. The
IIO core when done using this trigger will call `iio_trigger_put()` to drop
the reference count by 1.
Without the matching `iio_trigger_get()` in the driver the reference count
can reach 0 too early, the trigger gets freed while still in use and a
use-after-free occurs.
Fix this by getting a reference to the trigger before assigning it to the
IIO device.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47500 is a Linux kernel bug in the mma8452 IIO driver. A missing reference count increment can let a trigger object be freed while still in use, causing a use-after-free. Business urgency depends on whether affected Linux kernels actually use this driver.
Executive priority
Treat this as targeted kernel maintenance, not an internet-scale emergency based on current evidence. Prioritize embedded, appliance, or hardware-adjacent Linux assets that may use this driver, and fold remediation into normal kernel patch cycles unless vendor guidance raises urgency.
Technical view
The mma8452 driver assigns a trigger to struct iio_dev without first taking a matching iio_trigger_get() reference. When the IIO core later calls iio_trigger_put(), the reference count may drop to zero prematurely, freeing the trigger while it remains reachable.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the mma8452 IIO driver present and exercised. The CVE record lists affected Linux kernel version branches, but no product-specific downstream distribution status is provided.
Exploitation context
The provided sources do not report active exploitation, public exploit code, or KEV listing. The impact is described as kernel use-after-free, but practical exploitability, required privileges, and reachable attack paths are not established in the bundle.
Researcher notes
The core issue is lifetime management: missing iio_trigger_get() before assigning indio_dev->trig permits premature iio_trigger_put() cleanup. The bundle does not provide CVSS, CWE, exploit prerequisites, or downstream distro mapping, so exposure validation should be asset-specific.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check Linux vendor advisories for distribution-specific fixed kernel packages.
Prioritize systems that enable or load the mma8452 IIO driver.
Disable unused affected hardware support where vendor guidance allows.
Validation and detection
Inventory running kernel versions and loaded mma8452-related modules.
Compare kernel source or package changelogs against the referenced stable commits.
Confirm whether affected systems use IIO triggers with this driver.
Track vendor advisories for backported fixes and package status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47500 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.