CVE-2021-47437: iio: adis16475: fix deadlock on frequency set
In the Linux kernel, the following vulnerability has been resolved:
iio: adis16475: fix deadlock on frequency set
With commit 39c024b51b560
("iio: adis16475: improve sync scale mode handling"), two deadlocks were
introduced:
1) The call to 'adis_write_reg_16()' was not changed to it's unlocked
version.
2) The lock was not being released on the success path of the function.
This change fixes both these issues.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause a deadlock when setting frequency for the adis16475 Industrial I/O driver. The business impact appears availability-focused and likely narrow, tied to systems using this driver and affected kernel versions. The source bundle provides no CVSS score or broad-impact evidence.
Executive priority
Treat this as a targeted Linux kernel availability risk, not a confirmed emergency. Prioritize patch validation where affected kernels and adis16475-related hardware or driver use exist. Broader enterprise urgency is limited by the lack of CVSS, KEV, or exploitation evidence in the bundle.
Technical view
CVE-2021-47437 fixes two locking bugs introduced by commit 39c024b51b560 in the Linux kernel adis16475 driver: a locked register write path was used incorrectly, and a successful path failed to release the lock. Stable kernel commits are referenced as fixes.
Likely exposure
Exposure is most likely limited to Linux kernels containing the affected adis16475 driver change, especially listed versions around 5.13, 5.14.14, and 5.15. Systems not using this driver or related hardware path are less likely to be affected.
Exploitation context
The bundle does not cite active exploitation, public exploit use, or CISA KEV listing. The described failure mode is a kernel driver deadlock during frequency setting, suggesting denial-of-service potential, but access requirements are not established in the provided sources.
Researcher notes
The record identifies a regression-style locking flaw in a specific kernel driver. The evidence is sparse: no CWE, CVSS, exploitability detail, or access vector is provided. Analysis should focus on commit presence, downstream backports, and whether userspace can trigger the affected frequency-setting path.
Mitigation direction
Review vendor kernel advisories for CVE-2021-47437 applicability.
Update to a kernel build containing the referenced stable fixes.
Prioritize systems using the adis16475 Industrial I/O driver.
If updates are delayed, assess whether the driver is needed.
Track downstream distribution patches rather than relying only on upstream versions.
Validation and detection
Inventory Linux kernel versions against the affected range in the source bundle.
Check whether the adis16475 driver is present and used.
Confirm whether the referenced stable fix commits are included.
Review distribution security notes for backported fixes.
Record systems with relevant IIO sensor hardware for remediation tracking.
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-47437 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.