# CVE-2019-14835: Memory corruption in Linux kernel > A privileged guest user can exploit a buffer overflow in the Linux kernel's vhost migration logging to escalate privileges on the host. - **Severity:** High 7.2 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 17 Sep 2019 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-14835, GHSA-h3vw-f6h8-86mg, RHSA-2019:2827, RHSA-2019:2828, RHSA-2019:2829, RHSA-2019:2830, RHSA-2019:2854, RHSA-2019:2862, RHSA-2019:2863, RHSA-2019:2864, RHSA-2019:2865, RHSA-2019:2866, RHSA-2019:2867, RHSA-2019:2869, RHSA-2019:2889, RHSA-2019:2901, RHSA-2019:2924, SUSE-SU-2019:2572-1, SUSE-SU-2019:2613-1, UBUNTU-CVE-2019-14835 ## What is CVE-2019-14835? CVE-2019-14835 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 17 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A buffer overflow flaw was found, in versions from 2.6.34 to 5.2.x, in the way Linux kernel's vhost functionality that translates virtqueue buffers to IOVs, logged the buffer descriptors during migration. A privileged guest user able to pass descriptors with invalid length to the host when migration is underway, could use this flaw to increase their privileges on the host. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2019-14835? It affects 34 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `python-perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.23.1.el6 | | `kernel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `python-perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.23.1.el6 | | `kernel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-bootwrapper` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-ppc64` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | | `kernel-debuginfo-common-s390x` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.23.1.el6 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Huawei Imanager Neteco, Huawei Imanager Neteco 6000, Huawei Manageone, Linux kernel, Netapp Aff A700s Firmware, Netapp Data Availability Services, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H610s Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Netapp Hci Management Node, Netapp Service Processor and 14 more. ## How do I fix CVE-2019-14835? Apply the vendor's patch. ## Is CVE-2019-14835 being exploited? There is no known exploitation of CVE-2019-14835 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-14835 and fix it if it is affected. What it is: CVE-2019-14835 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 17 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-14835 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. 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-14835/ (Markdown: https://insights.sbomify.com/CVE-2019-14835/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-14835 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-14835 - OSV: https://osv.dev/vulnerability/CVE-2019-14835 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-14835/ Summaries are generated and may contain mistakes; the official description above is the record.