# CVE-2022-42896: Info Leak in l2cap_core in the Linux Kernel > Remote attackers within Bluetooth proximity can execute code or leak kernel memory via use-after-free flaws in the Linux kernel Bluetooth stack. - **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Nov 2022 - **Updated:** 14 Oct 2026 - **Also known as:** DEBIAN-CVE-2022-42896, GHSA-pvw8-76h2-7q32, RHSA-2023:3461, RHSA-2023:3462, RHSA-2023:3517, RHSA-2023:4230, UBUNTU-CVE-2022-42896, USN-5783-1 ## What is CVE-2022-42896? CVE-2022-42896 is a high-severity use after free vulnerability in Linux kernel, published on 23 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description There are use-after-free vulnerabilities in the Linux kernel's net/bluetooth/l2cap_core.c's l2cap_connect and l2cap_le_connect_req functions which may allow code execution and leaking kernel memory (respectively) remotely via Bluetooth. A remote attacker could execute code leaking kernel memory via Bluetooth if within proximity of the victim. We recommend upgrading past commit  https://www.google.com/url https://github.com/torvalds/linux/commit/711f8c3fb3db61897080468586b970c87c61d9e4 https://www.google.com/url Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2022-42896? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bpftool` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `bpftool-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-abi-stablelists` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-core` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-core` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-devel` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-modules` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-modules-extra` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-devel` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-doc` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-modules` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-modules-extra` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-tools` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-tools-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-tools-libs` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `perf` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `perf-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `python3-perf` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `python3-perf-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `bpftool` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `bpftool-debuginfo` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-abi-stablelists` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-core` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-core` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-debuginfo` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-devel` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-modules` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debug-modules-extra` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo-common-aarch64` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo-common-s390x` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:4.18.0-305.91.1.el8_4 | Products: Linux kernel. ## How do I fix CVE-2022-42896? Apply the vendor's patch. ## Is CVE-2022-42896 being exploited? There is no known exploitation of CVE-2022-42896 in the wild and no public exploit code. Public exploit code: - https://github.com/Satheesh575555/linux-4.19.72_CVE-2022-42896 (github_poc): https://github.com/Satheesh575555/linux-4.19.72_CVE-2022-42896 - https://github.com/Trinadh465/linux-4.19.72_CVE-2022-42896 (github_poc): https://github.com/Trinadh465/linux-4.19.72_CVE-2022-42896 ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-42896 and fix it if it is affected. What it is: CVE-2022-42896 is a high-severity use after free vulnerability in Linux kernel, published on 23 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-42896 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-42896/ (Markdown: https://insights.sbomify.com/CVE-2022-42896/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-42896 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-42896 - OSV: https://osv.dev/vulnerability/CVE-2022-42896 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-42896/ Summaries are generated and may contain mistakes; the official description above is the record.