CVE-2022-49953: iio: light: cm3605: Fix an error handling path in cm3605_probe()
In the Linux kernel, the following vulnerability has been resolved:
iio: light: cm3605: Fix an error handling path in cm3605_probe()
The commit in Fixes also introduced a new error handling path which should
goto the existing error handling path.
Otherwise some resources leak.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is an error-cleanup bug in the cm3605 light sensor driver. When device setup fails in one path, resources may not be released. The public record does not provide CVSS, confirmed impact, or exploitation evidence, so business urgency should be based on whether affected kernels and this driver exist in your fleet.
Executive priority
Handle through normal kernel maintenance unless affected embedded or hardware-adjacent systems are business critical. There is no sourced evidence of active exploitation, but incomplete severity data means owners should verify exposure rather than dismiss it.
Technical view
The bug is in cm3605_probe() under the Linux IIO light driver. A newly introduced error path failed to jump to the existing cleanup path, causing resource leakage. The sources identify affected Linux versions around 5.16 through 6.0 and two upstream stable commits as references/fixes.
Likely exposure
Exposure appears limited to Linux systems with affected kernel versions and the cm3605 IIO light sensor driver present, enabled, or relevant to hardware. General servers without this driver or hardware are less likely to be exposed, but distribution backports require vendor-specific verification.
Exploitation context
The source bundle does not cite active exploitation, public exploit use, KEV listing, or a detailed attacker model. Based on the description, the issue concerns resource cleanup during driver probe failure, not a documented remote attack path.
Researcher notes
Key evidence is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. Analysis should focus on the referenced kernel commits, affected kernel lineage, distro backports, and whether cm3605_probe() can be reached in local configurations.
Mitigation direction
Check vendor kernel advisories for CVE-2022-49953 applicability and fixed packages.
Update affected systems to a vendor kernel containing the referenced stable fixes.
Prioritize embedded, IoT, or sensor-bearing Linux systems using the cm3605 driver.
Track distribution backports instead of relying only on upstream version numbers.
Validation and detection
Inventory Linux kernel versions across affected asset classes.
Determine whether the cm3605 IIO light driver is built, loaded, or used.
Verify vendor kernel changelogs include the referenced stable commits or CVE fix.
Confirm vulnerability scanner findings clear after kernel updates.
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-2022-49953 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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.