CVE-2021-47620

Bluetooth: refactor malicious adv data check

MEDIUM

5.5

CVSS Score

Published: June 20, 2024 at 11:08 AM UTC

Updated: August 5, 2026 at 09:24 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: refactor malicious adv data check Check for out-of-bound read was being performed at the end of while num_reports loop, and would fill journal with false positives. Added check to beginning of loop processing so that it doesn't get checked after ptr has been advanced.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 4.4.3024.10 ≤ v < 4.14.2654.14.263 ≤ v < 4.14.2654.15 ≤ v < 4.19.2284.19.226 ≤ v < 4.19.2284.20 ≤ v < 5.4.1764.4.300 ≤ v < 4.4.3024.5 ≤ v < 4.9.3004.9.298 ≤ v < 4.9.3005.10.94 ≤ v < 5.10.965.11 ≤ v < 5.15.195.15.17 ≤ v < 5.15.195.16 ≤ v < 5.16.55.16.3 ≤ v < 5.16.55.4.174 ≤ v < 5.4.1765.5 ≤ v < 5.10.96185c77cbb53bc7481acc5a0b4e6119bbe393d56124161b9c43de966789d5956428f45002d10f878e2de0e6a71ceb056e17e4684dce8b7640367996f93a56ef719f0b9682afb8a86d64b2399e36faa4e64.14.263 4.19.226 4.4.300 4.9.29848acfa4daf167b7b6bd8bef474e90c2282a5f4a1491432394b22e585a185ffca49086e4046aae5.10.94 5.15.17 5.16.3 5.4.174640a476e38fce6c70c738ac09e5167e34f5703037d4238edd3bf8b8c75571cc3b382bc10438ac588ffc9019bd991707701273c2e5d8aed472229fc4d

Vendor states this is fixed in 305e92f525450f3e1b5f5c9dc7eadb152d66a082 (fixed)

Vendor states this is fixed in 5a539c08d743d9910631448da78af5e961664c0e (fixed)

Vendor states this is fixed in 5c968affa804ba98c3c603f37ffea6fba618025e (fixed)

Vendor states this is fixed in 7889b38a7f21ed19314f83194622b195d328465c (fixed)

Vendor states this is fixed in 835d3706852537bf92eb23eb8635b8dee0c0aa67 (fixed)

Vendor states this is fixed in 83d5196b65d1b29e27d7dd16a3b9b439fb1d2dba (fixed)

Vendor states this is fixed in 8819f93cd4a443dfe547aa622b21f723757df3fb (fixed)

Vendor states this is fixed in 899663be5e75dc0174dc8bda0b5e6826edf0b29a (fixed)

Vendor states this is fixed in bcea886771c3f22a590c8c8b9139a107bd7f1e1c (fixed)

Affected range stops below 4.14.265, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.19.228, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.4.302, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.9.300, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.10.96, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.15.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.16.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.176, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references