# CVE-2019-19768: Use after free in n/a > A use-after-free vulnerability in the Linux kernel's blktrace function allows attackers to potentially execute code or escalate privileges. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Dec 2019 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-19768, GHSA-j7c5-8q8x-hgwf, RHSA-2020:1966, UBUNTU-CVE-2019-19768 ## What is CVE-2019-19768? CVE-2019-19768 is a high-severity use after free vulnerability in Linux kernel, published on 12 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_trace function in kernel/trace/blktrace.c (which is used to fill out a blk_io_trace structure and place it in a per-cpu sub-buffer). Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2019-19768? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bpftool` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `bpftool-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-abi-whitelists` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-core` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debug` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debug-core` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debug-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debug-devel` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debug-modules` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debug-modules-extra` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-devel` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-doc` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-modules` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-modules-extra` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-tools` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-tools-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `kernel-tools-libs` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `perf` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `perf-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `python3-perf` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | | `python3-perf-debuginfo` | Red Hat:rhel_e4s:8.0::baseos | All versions | 0:4.18.0-80.18.1.el8_0 | Products: Linux kernel. ## How do I fix CVE-2019-19768? Apply the vendor's patch. ## Is CVE-2019-19768 being exploited? There is no known exploitation of CVE-2019-19768 in the wild and no public exploit code. ## 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-2019-19768 and fix it if it is affected. What it is: CVE-2019-19768 is a high-severity use after free vulnerability in Linux kernel, published on 12 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-19768 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-2019-19768/ (Markdown: https://insights.sbomify.com/CVE-2019-19768/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-19768 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-19768 - OSV: https://osv.dev/vulnerability/CVE-2019-19768 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-19768/ Summaries are generated and may contain mistakes; the official description above is the record.