From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64166: firmware: arm_ffa: Check for NULL FF-A ID table while driver registration
Date: Sun, 19 Jul 2026 17:40:28 +0200 [thread overview]
Message-ID: <2026071935-CVE-2026-64166-98a5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
firmware: arm_ffa: Check for NULL FF-A ID table while driver registration
The bus match callback assumes that every FF-A driver provides an
id_table and dereferences it unconditionally. Enforce that contract at
registration time so a buggy client driver cannot crash the bus during
match.
The Linux kernel CVE team has assigned CVE-2026-64166 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 5.15.209 with commit f98f131256beaddd51ad468e95d90d857fef12bf
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 6.1.175 with commit bc499d1acddbb75b5b4bce05f5296dd8ef9611fd
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 6.6.142 with commit adfff93d08a2e12ecf2a1eba272d18bc749f13c0
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 6.12.92 with commit 34f59211984f66788390e7469f3e99d3796db4a8
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 6.18.34 with commit 820245d86ce58898fb48b4fefc77d0cafc02801d
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 7.0.11 with commit 198f6c86d508ed562f07dc00276cac6dbb5dd3bf
Issue introduced in 5.14 with commit 92743071464fca5acbbe812d9a0d88de3eaaad36 and fixed in 7.1 with commit 0a5e695095c557d2380131b613dea4e8d90371be
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-64166
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/bus.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/f98f131256beaddd51ad468e95d90d857fef12bf
https://git.kernel.org/stable/c/bc499d1acddbb75b5b4bce05f5296dd8ef9611fd
https://git.kernel.org/stable/c/adfff93d08a2e12ecf2a1eba272d18bc749f13c0
https://git.kernel.org/stable/c/34f59211984f66788390e7469f3e99d3796db4a8
https://git.kernel.org/stable/c/820245d86ce58898fb48b4fefc77d0cafc02801d
https://git.kernel.org/stable/c/198f6c86d508ed562f07dc00276cac6dbb5dd3bf
https://git.kernel.org/stable/c/0a5e695095c557d2380131b613dea4e8d90371be
reply other threads:[~2026-07-19 15:47 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=2026071935-CVE-2026-64166-98a5@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