# CVE-2018-5848: Integer overflow in Android for MSM, Firefox OS for MSM, QRD Android > An integer overflow in the wmi_set_ie function allows attackers to trigger a buffer overflow, potentially leading to code execution or privilege escalation. - **Severity:** High 7.8 (`CVSS:3.0/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:** 12 Jun 2018 - **Updated:** 17 Sep 2024 - **Also known as:** DEBIAN-CVE-2018-5848, GHSA-hf9h-mjmm-hjj4, SUSE-SU-2018:4127-1, SUSE-SU-2018:4208-1, UBUNTU-CVE-2018-5848 ## What is CVE-2018-5848? CVE-2018-5848 is a high-severity vulnerability in Debian Debian Linux, published on 12 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the function wmi_set_ie(), the length validation code does not handle unsigned integer overflow properly. As a result, a large value of the 'ie_len' argument can cause a buffer overflow in all Android releases from CAF (Android for MSM, Firefox OS for MSM, QRD Android) using the Linux Kernel. Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2018-5848? It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kgraft-patch-SLE12-SP3_Update_10` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 9-2.1 | | `kgraft-patch-SLE12-SP3_Update_11` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 9-2.1 | | `kgraft-patch-SLE12-SP3_Update_12` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 7-2.1 | | `kgraft-patch-SLE12-SP3_Update_13` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 7-2.1 | | `kgraft-patch-SLE12-SP3_Update_6` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 12-2.1 | | `kgraft-patch-SLE12-SP3_Update_7` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 12-2.1 | | `kgraft-patch-SLE12-SP3_Update_8` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 10-2.1 | | `kgraft-patch-SLE12-SP3_Update_9` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 10-2.1 | | `kgraft-patch-SLE12-SP2_Update_16` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 12-2.1 | | `kgraft-patch-SLE12-SP2_Update_17` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 12-2.1 | | `kgraft-patch-SLE12-SP2_Update_18` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 10-2.1 | | `kgraft-patch-SLE12-SP2_Update_19` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 10-2.1 | | `kgraft-patch-SLE12-SP2_Update_20` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 9-2.1 | | `kgraft-patch-SLE12-SP2_Update_21` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 8-2.1 | | `kgraft-patch-SLE12-SP2_Update_22` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 8-2.1 | | `kgraft-patch-SLE12-SP2_Update_16` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 12-2.1 | | `kgraft-patch-SLE12-SP2_Update_17` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 12-2.1 | | `kgraft-patch-SLE12-SP2_Update_18` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 10-2.1 | | `kgraft-patch-SLE12-SP2_Update_19` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 10-2.1 | | `kgraft-patch-SLE12-SP2_Update_20` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 9-2.1 | | `kgraft-patch-SLE12-SP2_Update_21` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 8-2.1 | | `kgraft-patch-SLE12-SP2_Update_22` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 8-2.1 | Products: Debian Debian Linux, Google Android, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, Redhat Virtualization Host. ## How do I fix CVE-2018-5848? Apply the vendor's patch. ## Is CVE-2018-5848 being exploited? There is no known exploitation of CVE-2018-5848 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-5848 and fix it if it is affected. What it is: CVE-2018-5848 is a high-severity vulnerability in Debian Debian Linux, published on 12 Jun 2018. 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-2018-5848 in the wild and no public exploit code. Affected product: Debian Debian 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-2018-5848/ (Markdown: https://insights.sbomify.com/CVE-2018-5848/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-5848 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-5848 - OSV: https://osv.dev/vulnerability/CVE-2018-5848 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-5848/ Summaries are generated and may contain mistakes; the official description above is the record.