From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64081: firmware: arm_ffa: Validate framework notification message layout
Date: Sun, 19 Jul 2026 17:39:03 +0200 [thread overview]
Message-ID: <2026071915-CVE-2026-64081-cb26@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
firmware: arm_ffa: Validate framework notification message layout
Framework notifications carry an indirect message in the shared RX
buffer. Validate the reported offset and size before using them, reject
zero-length payloads, and ensure that any non-header payload starts at
the UUID field rather than in the middle of the message header.
Use the validated offset and size values for both kmemdup() and the UUID
parsing path so malformed firmware data cannot drive an out-of-bounds
read or an oversized allocation.
The Linux kernel CVE team has assigned CVE-2026-64081 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 285a5ea0f542db94c3ed11e01a71abb47d15cbf5 and fixed in 6.18.34 with commit 3c51d99449dc5a01c08a7fce6071d6721f5aac83
Issue introduced in 6.15 with commit 285a5ea0f542db94c3ed11e01a71abb47d15cbf5 and fixed in 7.0.11 with commit 76eb90e2b03de147e12ab68ea8afd8ea0342df0a
Issue introduced in 6.15 with commit 285a5ea0f542db94c3ed11e01a71abb47d15cbf5 and fixed in 7.1 with commit 4a1cc9e96b311d2609a6f963a5e35bd4ae730d97
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-64081
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/firmware/arm_ffa/driver.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/3c51d99449dc5a01c08a7fce6071d6721f5aac83
https://git.kernel.org/stable/c/76eb90e2b03de147e12ab68ea8afd8ea0342df0a
https://git.kernel.org/stable/c/4a1cc9e96b311d2609a6f963a5e35bd4ae730d97
reply other threads:[~2026-07-19 15:43 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=2026071915-CVE-2026-64081-cb26@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