From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path
Date: Fri, 8 May 2026 16:21:24 +0200 [thread overview]
Message-ID: <2026050824-CVE-2026-43355-db72@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-43355 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.7 with commit 1f0477f18306c018a954e4f333690a9d0f7efc76 and fixed in 5.10.253 with commit 1eb3af4f59e09323788860a9155e9766b12891e5
Issue introduced in 4.7 with commit 1f0477f18306c018a954e4f333690a9d0f7efc76 and fixed in 6.1.167 with commit 424bf90e87134effe4bd932608a15286493b11ab
Issue introduced in 4.7 with commit 1f0477f18306c018a954e4f333690a9d0f7efc76 and fixed in 6.6.130 with commit fc77e0a5600e620a2ae51ec78933162fb217b20b
Issue introduced in 4.7 with commit 1f0477f18306c018a954e4f333690a9d0f7efc76 and fixed in 6.18.19 with commit aae572ddc28578af476cce7da3faec0395ef0bf0
Issue introduced in 4.7 with commit 1f0477f18306c018a954e4f333690a9d0f7efc76 and fixed in 6.19.9 with commit 33661bfc85c14836bfef4425a74b0ca2df4bb5ad
Issue introduced in 4.7 with commit 1f0477f18306c018a954e4f333690a9d0f7efc76 and fixed in 7.0 with commit dd72e6c3cdea05cad24e99710939086f7a113fb5
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-43355
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/iio/light/bh1780.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1eb3af4f59e09323788860a9155e9766b12891e5
https://git.kernel.org/stable/c/424bf90e87134effe4bd932608a15286493b11ab
https://git.kernel.org/stable/c/fc77e0a5600e620a2ae51ec78933162fb217b20b
https://git.kernel.org/stable/c/aae572ddc28578af476cce7da3faec0395ef0bf0
https://git.kernel.org/stable/c/33661bfc85c14836bfef4425a74b0ca2df4bb5ad
https://git.kernel.org/stable/c/dd72e6c3cdea05cad24e99710939086f7a113fb5
reply other threads:[~2026-05-08 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050824-CVE-2026-43355-db72@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox