A heap buffer overflow flaw was found in the way the Linux kernel Bluetooth implementation processed extended advertising report events. A remote attacker in adjacent range could use this flaw to crash the system causing denial od service or potentially execute arbitrary code on the system by sending a specially crafted Bluetooth packet.
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1888450]
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-24490
This was resolved for Fedora with the 5.7.13 stable kernel update.
External References: https://access.redhat.com/security/vulnerabilities/BleedingTooth https://github.com/google/security-research/security/advisories/GHSA-ccx2-w2r4-x649 https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=a2ec905d1e160a33b2e210e45ad30445ef26ce0e https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00435.html
Mitigation: The only way to mitigate these vulnerabilities on the operating system level is to disable the Bluetooth functionality via blacklisting kernel modules in the Linux kernel. The kernel modules can be prevented from being loaded by using system-wide modprobe rules. How to disable Bluetooth modules instructions are available on the Customer Portal at https://access.redhat.com/solutions/2682931. Alternatively Bluetooth can be disabled within the hardware or at BIOS level which will also provide an effective mitigation as the kernel will not be able to detect that Bluetooth hardware is present on the system.
Statement: This issue is rated as having Moderate impact because the system needs to be actively scanning while the attacker is sending the advertisements in order to be exploited. This issue only affects the Linux kernel version as shipped with the Red Hat Enterprise Linux 8.3 GA release, kernel-4.18.0-240.el8 (and any kernel derived from this release such as kernel rt-4.18.0-240.rt7.54.el8). Red Hat was unable to include the fixes in the GA release, as the Red Hat Enterprise Linux 8.3 GA release was in its final stages of release preparation when CVE-2020-24490 was made public. All of the subsequent Red Hat Enterprise Linux 8 kernel versions, including the version included in the so-called 0day (released on the same day or very close to that day) erratum, contain the fix, thus immune to this issue.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:4686 https://access.redhat.com/errata/RHSA-2020:4686
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:4685 https://access.redhat.com/errata/RHSA-2020:4685