[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025071015-CVE-2025-38315-ccfc@gregkh>
Date: Thu, 10 Jul 2025 09:42:56 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38315: Bluetooth: btintel: Check dsbr size from EFI variable
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btintel: Check dsbr size from EFI variable
Since the size of struct btintel_dsbr is already known, we can just
start there instead of querying the EFI variable size. If the final
result doesn't match what we expect also fail. This fixes a stack buffer
overflow when the EFI variable is larger than struct btintel_dsbr.
The Linux kernel CVE team has assigned CVE-2025-38315 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit eb9e749c0182affafadfbe5ded4503c4b5a9b57c and fixed in 6.12.34 with commit 9427f6081f37c795a8bd29d0ee72a4da3bd64af8
Issue introduced in 6.11 with commit eb9e749c0182affafadfbe5ded4503c4b5a9b57c and fixed in 6.15.3 with commit 7b8526bb489780ccc0caffc446ecabec83cfe568
Issue introduced in 6.11 with commit eb9e749c0182affafadfbe5ded4503c4b5a9b57c and fixed in 6.16-rc1 with commit 3aa1dc3c9060e335e82e9c182bf3d1db29220b1b
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-38315
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/bluetooth/btintel.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/9427f6081f37c795a8bd29d0ee72a4da3bd64af8
https://git.kernel.org/stable/c/7b8526bb489780ccc0caffc446ecabec83cfe568
https://git.kernel.org/stable/c/3aa1dc3c9060e335e82e9c182bf3d1db29220b1b
Powered by blists - more mailing lists