From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46326: iio: pressure: mprls0025pa: fix spi_transfer struct initialisation
Date: Tue, 9 Jun 2026 14:25:09 +0200 [thread overview]
Message-ID: <2026060909-CVE-2026-46326-2f79@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: pressure: mprls0025pa: fix spi_transfer struct initialisation
Make sure that the spi_transfer struct is zeroed out before use.
The Linux kernel CVE team has assigned CVE-2026-46326 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit a0858f0cd28e822b91376ae288d5548bc1847531 and fixed in 6.12.75 with commit 72158f9ae29a9e56d0f9704ce461a866feaf9925
Issue introduced in 6.9 with commit a0858f0cd28e822b91376ae288d5548bc1847531 and fixed in 6.18.14 with commit 664ffdf34c01810085e4d85508b361c3fdd2ab40
Issue introduced in 6.9 with commit a0858f0cd28e822b91376ae288d5548bc1847531 and fixed in 6.19.4 with commit 9080c7ac30f5f8f8fcb7b27b56df60fea7909c21
Issue introduced in 6.9 with commit a0858f0cd28e822b91376ae288d5548bc1847531 and fixed in 7.0 with commit 1e0ac56c92e26115cbc8cfc639843725cb3a7d6a
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-46326
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/pressure/mprls0025pa_spi.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/72158f9ae29a9e56d0f9704ce461a866feaf9925
https://git.kernel.org/stable/c/664ffdf34c01810085e4d85508b361c3fdd2ab40
https://git.kernel.org/stable/c/9080c7ac30f5f8f8fcb7b27b56df60fea7909c21
https://git.kernel.org/stable/c/1e0ac56c92e26115cbc8cfc639843725cb3a7d6a
reply other threads:[~2026-06-09 12:26 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=2026060909-CVE-2026-46326-2f79@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