From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72158: fpga: dfl: add bounds check in dfh_get_param_size()
Date: Sat, 15 Aug 2026 15:03:57 +0900 [thread overview]
Message-ID: <2026081535-CVE-2026-72158-d66b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fpga: dfl: add bounds check in dfh_get_param_size()
dfh_get_param_size() can return a parameter size larger than the feature
region because the loop bounds check is evaluated before incrementing
size. If the EOP (End of Parameters) bit is set in the same iteration,
the inflated size is returned without re-validation against max.
This can cause create_feature_instance() to call memcpy_fromio() with a
size exceeding the ioremap'd region when a malicious FPGA device provides
crafted DFHv1 parameter headers.
Add a bounds check after the size increment to ensure the accumulated
size never exceeds the feature boundary.
The Linux kernel CVE team has assigned CVE-2026-72158 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.3 with commit 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and fixed in 6.6.145 with commit b2f6220e929b2a43605331d0139e65dc1640c05c
Issue introduced in 6.3 with commit 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and fixed in 6.12.97 with commit 3b622aa447cf26104f96a8be39539367863bc6b6
Issue introduced in 6.3 with commit 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and fixed in 6.18.40 with commit 012683accbb7d2bcf1264f2a0ecd6aa1dcea4d68
Issue introduced in 6.3 with commit 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and fixed in 7.1.5 with commit f3df5386e3bb54626c117bd85e0158d45fb4aea9
Issue introduced in 6.3 with commit 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and fixed in 7.2-rc1 with commit 9e8bc49f91f3f81d957c4f1c1f09fe94e2f88f6a
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-72158
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/fpga/dfl.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/b2f6220e929b2a43605331d0139e65dc1640c05c
https://git.kernel.org/stable/c/3b622aa447cf26104f96a8be39539367863bc6b6
https://git.kernel.org/stable/c/012683accbb7d2bcf1264f2a0ecd6aa1dcea4d68
https://git.kernel.org/stable/c/f3df5386e3bb54626c117bd85e0158d45fb4aea9
https://git.kernel.org/stable/c/9e8bc49f91f3f81d957c4f1c1f09fe94e2f88f6a
reply other threads:[~2026-08-15 6:14 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=2026081535-CVE-2026-72158-d66b@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.