CVE-2020-25662 json
A Red Hat only CVE-2020-12352 regression issue was found in the way the Linux kernel's Bluetooth stack implementation handled the initializ…
published 2020-11-05 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-18324
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
A Red Hat only CVE-2020-12352 regression issue was found in the way the Linux kernel's Bluetooth stack implementation handled the initialization of stack memory when handling certain AMP packets. This flaw allows a remote attacker in an adjacent range to leak small portions of stack memory on the system by sending specially crafted AMP packets. The highest threat from this vulnerability is to data confidentiality.
Patch / fix
- kernel RHEL 8 4.18.0-240.1.1.el8_3
- perf RHEL 8 4.18.0-240.1.1.el8_3
- bpftool RHEL 8 4.18.0-240.1.1.el8_3
- kernel-core RHEL 8 4.18.0-240.1.1.el8_3
- kernel-tools RHEL 8 4.18.0-240.1.1.el8_3
- python3-perf RHEL 8 4.18.0-240.1.1.el8_3
- kernel-modules RHEL 8 4.18.0-240.1.1.el8_3
- kernel-zfcpdump RHEL 8 4.18.0-240.1.1.el8_3
red hat advisories RHSA-2020:4685RHSA-2020:4686
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-25662 updated cvss 5.3
kernel: Red Hat only CVE-2020-12352 regression
-
Red Hat CodeReady Linux Builder (v. 8) kernel-debuginfo-common-x86_64 4.18.0-240.1.1.el8_3, kernel-debuginfo-common-aarch64 4.18.0-240.1.1.el8_3, kernel-debuginfo-common-ppc64le 4.18.0-240.1.1.el8_3 Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-240.1.1.el8_3, kernel 4.18.0-240.1.1.el8_3, bpftool 4.18.0-240.1.1.el8_3, kernel-core 4.18.0-240.1.1.el8_3, kernel-tools 4.18.0-240.1.1.el8_3, python3-perf 4.18.0-240.1.1.el8_3, +15 morefixed: vendor fix RHSA-2020:4685
-
Red Hat Enterprise Linux Real Time (v. 8) kernel-rt 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-core 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-modules 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-debug-core 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-debug-modules 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-modules-extra 4.18.0-240.1.1.rt7.55.el8_3, +2 more Red Hat Enterprise Linux Real Time for NFV (v. 8) kernel-rt 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-kvm 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-core 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-modules 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-debug-kvm 4.18.0-240.1.1.rt7.55.el8_3, kernel-rt-debug-core 4.18.0-240.1.1.rt7.55.el8_3, +4 morefixed: vendor fix RHSA-2020:4686
-
Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, kernel-alt, python-perf, +9 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 3.3 | AV:A/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Red Hat kernel
Classification
References
-
access.redhat.com
/security/vulnerabilities/BleedingTooth
vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2020-25662
issue-tracking, mitigation, vendor-advisory
-
access.redhat.com
/security/cve/CVE-2020-12352
mitigation, vendor-advisory
Sources
- CVE List CVE-2020-25662
- NVD CVE-2020-25662
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.