# CVE-2019-0155: Privilege escalation in 2019.2 IPU – Intel(R) Graphics Driver for Windows* and Linux > An authenticated local attacker can escalate privileges due to insufficient access control in Intel processor graphics subsystems. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-0155, GHSA-8885-wr7g-q9vx, RHSA-2019:3870, RHSA-2019:3871, RHSA-2019:3872, RHSA-2019:3873, RHSA-2019:3877, RHSA-2019:3878, RHSA-2019:3883, RHSA-2019:3887, RHSA-2019:3889, RHSA-2019:3908, UBUNTU-CVE-2019-0155, USN-4184-2, USN-4185-3, USN-4186-3 ## What is CVE-2019-0155? CVE-2019-0155 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 14 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Insufficient access control in a subsystem for Intel (R) processor graphics in 6th, 7th, 8th and 9th Generation Intel(R) Core(TM) Processor Families; Intel(R) Pentium(R) Processor J, N, Silver and Gold Series; Intel(R) Celeron(R) Processor J, N, G3900 and G4900 Series; Intel(R) Atom(R) Processor A and E3900 Series; Intel(R) Xeon(R) Processor E3-1500 v5 and v6, E-2100 and E-2200 Processor Families; Intel(R) Graphics Driver for Windows before 26.20.100.6813 (DCH) or 26.20.100.6812 and before 21.20.x.5077 (aka15.45.5077), i915 Linux Driver for Intel(R) Processor Graphics before versions 5.4-rc7, 5.3.11, 4.19.84, 4.14.154, 4.9.201, 4.4.201 may allow an authenticated user to potentially enable escalation of privilege via local access. ## Which versions are affected by CVE-2019-0155? It affects 357 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `python-perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-754.24.3.el6 | | `kernel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `python-perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-754.24.3.el6 | | `kernel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-bootwrapper` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-ppc64` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | | `kernel-debuginfo-common-s390x` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-754.24.3.el6 | Products: Canonical Ubuntu Linux, Intel Atom X5-E3930 Firmware, Intel Atom X5-E3940 Firmware, Intel Atom X7-E3950 Firmware, Intel Celeron G3900 Firmware, Intel Celeron G3900e Firmware, Intel Celeron G3900t Firmware, Intel Celeron G3900te Firmware, Intel Celeron G3902e Firmware, Intel Celeron G3920 Firmware, Intel Celeron G3930 Firmware, Intel Celeron G3930e Firmware, Intel Celeron G3930t Firmware, Intel Celeron G3930te Firmware, Intel Celeron G3950 Firmware, Intel Celeron G4900 Firmware, Intel Celeron G4900t Firmware, Intel Celeron G4920 Firmware, Intel Celeron G4930 Firmware, Intel Celeron G4930e Firmware and 337 more. ## How do I fix CVE-2019-0155? Apply the vendor's patch. ## Is CVE-2019-0155 being exploited? There is no known exploitation of CVE-2019-0155 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-0155 and fix it if it is affected. What it is: CVE-2019-0155 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 14 Nov 2019. 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-2019-0155 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-0155/ (Markdown: https://insights.sbomify.com/CVE-2019-0155/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0155 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0155 - OSV: https://osv.dev/vulnerability/CVE-2019-0155 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-0155/ Summaries are generated and may contain mistakes; the official description above is the record.