From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43357: iio: gyro: mpu3050-core: fix pm_runtime error handling
Date: Fri, 8 May 2026 16:21:26 +0200 [thread overview]
Message-ID: <2026050824-CVE-2026-43357-4d3f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: gyro: mpu3050-core: fix pm_runtime error handling
The return value of pm_runtime_get_sync() is not checked, allowing
the driver to access hardware that may fail to resume. The device
usage count is also unconditionally incremented. Use
pm_runtime_resume_and_get() which propagates errors and avoids
incrementing the usage count on failure.
In preenable, add pm_runtime_put_autosuspend() on set_8khz_samplerate()
failure since postdisable does not run when preenable fails.
The Linux kernel CVE team has assigned CVE-2026-43357 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 5.10.253 with commit 935f57dd43492240e1ca220dd065d624efece6be
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 5.15.203 with commit 8544c488e50206f00630a8bbba43d2c8bd290345
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 6.1.167 with commit 35f54e7bcb1eccdc6e5bff06580eeef2e0ff3677
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 6.6.130 with commit 2a86a396aa001a9f9ba2d37dda36573a76f17c90
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 6.12.78 with commit 66c0d1d600e7be034959cf49edab104cb5a39258
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 6.18.19 with commit 42685cf96e28262e0b84d74447f3d99f3f6a72e0
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 6.19.9 with commit 7a3dec5b265cf87678b10c98a72a435a8e769bb7
Issue introduced in 4.10 with commit 3904b28efb2c780c23dcddfb87e07fe0230661e5 and fixed in 7.0 with commit acc3949aab3e8094641a9c7c2768de1958c88378
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-43357
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/gyro/mpu3050-core.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/935f57dd43492240e1ca220dd065d624efece6be
https://git.kernel.org/stable/c/8544c488e50206f00630a8bbba43d2c8bd290345
https://git.kernel.org/stable/c/35f54e7bcb1eccdc6e5bff06580eeef2e0ff3677
https://git.kernel.org/stable/c/2a86a396aa001a9f9ba2d37dda36573a76f17c90
https://git.kernel.org/stable/c/66c0d1d600e7be034959cf49edab104cb5a39258
https://git.kernel.org/stable/c/42685cf96e28262e0b84d74447f3d99f3f6a72e0
https://git.kernel.org/stable/c/7a3dec5b265cf87678b10c98a72a435a8e769bb7
https://git.kernel.org/stable/c/acc3949aab3e8094641a9c7c2768de1958c88378
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-43357-4d3f@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