CVE-2022-3564 — Linux Kernel Bluetooth l2cap_core.c l2cap_reassemble_sdu use after free
A vulnerability classified as critical was found in Linux Kernel. Affected by this vulnerability is the function l2cap_reassemble_sdu of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-211087.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1.4% (30-day exploitation probability)+11
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux Kernel, Netapp H300s Firmware…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux Kernel | ≥ 3.6 and < 4.9.333≥ 4.10 and < 4.14.299≥ 4.15 and < 4.19.265≥ 4.20 and < 5.4.224≥ 5.5.0 and < 5.10.154≥ 5.11 and < 5.15.78≥ 5.16 and < 6.0.8 | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.0 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.1 | CVSS 3.1 | High | 1.2 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | 2.1 | 3.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.43%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- Affected products added · linux/linux kernel, debian/debian linux, netapp/h300s firmware, netapp/h500s firmware, netapp/h700s firmware, netapp/h41
- CVSS changed · 7.1
- Source status changed · → Modified
- Record created in this database
- 2022
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
8 on the record
- git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/
- github.com/advisories/GHSA-hjfq-c3jw-r92p
- security.netapp.com/advisory/ntap-20221223-0001/
- nvd.nist.gov/vuln/detail/CVE-2022-3564
- lists.debian.org/debian-lts-announce/2022/12/msg00031.html
- vuldb.com/
- cert-portal.siemens.com/productcert/html/ssa-794697.html
- lists.debian.org/debian-lts-announce/2022/12/msg00034.html
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-98164 KVM: x86/mmu: Check write tracking in all address spaces 16d
- High CVE-2026-98163 cgroup: Avoid iteration of dying tasks with zero refcount 19d
- Medium CVE-2026-98162 smb/server: fix tree connection leak in smb2_tree_connect() 20d
- Medium CVE-2026-98160 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs… 20d
- Medium CVE-2026-98161 Improper Check for Unusual or Exceptional Conditions in Linux Linux Kernel 20d
- Medium CVE-2026-100079 Missing Release of Resource after Effective Lifetime in Linux Linux Kernel 20d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-3564 is "Linux Kernel Bluetooth l2cap_core.c l2cap_reassemble_sdu use after free", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 1.43% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.