[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120435-CVE-2025-40266-30a1@gregkh>
Date: Thu, 4 Dec 2025 16:57:47 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40266: KVM: arm64: Check the untrusted offset in FF-A memory share
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Check the untrusted offset in FF-A memory share
Verify the offset to prevent OOB access in the hypervisor
FF-A buffer in case an untrusted large enough value
[U32_MAX - sizeof(struct ffa_composite_mem_region) + 1, U32_MAX]
is set from the host kernel.
The Linux kernel CVE team has assigned CVE-2025-40266 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.118 with commit fc3139d9f4c1fe1c7d5f25f99676bd8e9c6a1041
Fixed in 6.12.60 with commit bc1909ef38788f2ee3d8011d70bf029948433051
Fixed in 6.17.10 with commit f9f1aed6c8a3427900da3121e1868124854569c3
Fixed in 6.18 with commit 103e17aac09cdd358133f9e00998b75d6c1f1518
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-2025-40266
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:
arch/arm64/kvm/hyp/nvhe/ffa.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/fc3139d9f4c1fe1c7d5f25f99676bd8e9c6a1041
https://git.kernel.org/stable/c/bc1909ef38788f2ee3d8011d70bf029948433051
https://git.kernel.org/stable/c/f9f1aed6c8a3427900da3121e1868124854569c3
https://git.kernel.org/stable/c/103e17aac09cdd358133f9e00998b75d6c1f1518
Powered by blists - more mailing lists