In the Linux kernel, the following vulnerability has been resolved:
iio: light: bh1780: fix PM runtime leak on error path
Move pm_runtime_put_autosuspend() before the error check to ensure
the PM runtime reference count is always decremented after
pm_runtime_get_sync(), regardless of whether the read operation
succeeds or fails.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43355 is a Linux kernel bug in the BH1780 light sensor driver. A failed sensor read can leave a power-management reference unreleased. The public record does not provide CVSS, confirmed impact, or exploitation evidence. Business urgency depends on whether your Linux devices use this specific sensor driver and affected kernel builds.
Executive priority
Treat as targeted kernel maintenance, not an emergency, unless your products use this sensor driver. Ask platform owners to confirm exposure and roll the vendor-supported kernel fix into normal patch cycles. Escalate priority for embedded devices where power-management failures affect reliability.
Technical view
The issue is in the Linux IIO light driver bh1780. The fix moves pm_runtime_put_autosuspend() before the error check so pm_runtime_get_sync() is balanced whether the read succeeds or fails. This addresses a PM runtime reference leak on an error path. The CVE record lists Linux kernel affected versions and stable kernel commit references.
Likely exposure
Exposure is likely limited to Linux systems with the bh1780 IIO light sensor driver in use on affected kernel versions. Servers and cloud workloads without this hardware or driver are less likely to be exposed. Vendor backports may change apparent version exposure, so distribution-specific kernel advisories should be checked.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not marked KEV. The sources describe a kernel bug fix, not a public exploit. Practical impact is unclear from the record, but the flaw concerns resource accounting in a hardware driver error path.
Researcher notes
The record lacks CVSS, CWE, exploitability details, and concrete impact beyond a PM runtime leak. Analysis should focus on reachable read error paths in bh1780 and distribution backport status. Avoid assuming broader Linux exposure without confirming driver presence and hardware relevance.
Mitigation direction
Update to a vendor kernel containing the linked stable fixes.
Check your Linux distribution advisory for backported fixes.
Prioritize embedded or hardware platforms using the BH1780 sensor.
If no vendor fix is available, monitor vendor kernel guidance.
Validation and detection
Inventory Linux kernel versions across affected device fleets.
Determine whether the bh1780 driver is present or enabled.
Confirm whether linked stable commits are included in your kernel.
Review vendor changelogs for CVE-2026-43355 backports.
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-2026-43355 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
9Source 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.
May 8, 2026, 14:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.