From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98658: iio: proximity: aw96103: validate firmware data length
Date: Sun, 18 Oct 2026 17:43:53 +0200 [thread overview]
Message-ID: <2026101854-CVE-2026-98658-e804@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: proximity: aw96103: validate firmware data length
The firmware parser reads a length from the binary header and then uses
it to walk six-byte register/value entries. A truncated firmware image
can make the parser read beyond the copied firmware buffer. A value
smaller than the four-byte count field also underflows, producing a very
large length.
Read the little-endian field with get_unaligned_le32(), as previously
proposed by David Lechner. Validate the header size, reject an
underflowed length, ensure the resulting payload is contained in the
firmware image, and require it to contain whole register/value entries.
The Linux kernel CVE team has assigned CVE-2026-98658 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 07b241262dcad07671c444ca955903325de28e9e and fixed in 6.12.113 with commit 4a9b9f2d4e26589afd0ac099c8e5593170dd5ac7
Issue introduced in 6.12 with commit 07b241262dcad07671c444ca955903325de28e9e and fixed in 6.18.56 with commit 6501b032be217ecf47e793b78a05078cf0b604ad
Issue introduced in 6.12 with commit 07b241262dcad07671c444ca955903325de28e9e and fixed in 7.2.10 with commit 815ae0b73b69ace207b6bbf7ef428b06491c3ddb
Issue introduced in 6.12 with commit 07b241262dcad07671c444ca955903325de28e9e and fixed in 7.3-rc6 with commit 1a7c522a35477d70320bd64aba8e9de0c1058c6f
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-98658
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/proximity/aw96103.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/4a9b9f2d4e26589afd0ac099c8e5593170dd5ac7
https://git.kernel.org/stable/c/6501b032be217ecf47e793b78a05078cf0b604ad
https://git.kernel.org/stable/c/815ae0b73b69ace207b6bbf7ef428b06491c3ddb
https://git.kernel.org/stable/c/1a7c522a35477d70320bd64aba8e9de0c1058c6f
reply other threads:[~2026-10-18 15:48 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=2026101854-CVE-2026-98658-e804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.