# CVE-2018-5390: Denial of service in Linux Kernel > Remote attackers can cause denial of service in Linux kernels by forcing expensive TCP queue operations on incoming packets. - **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:** 6 Aug 2018 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-5390, GHSA-grv8-gqh3-fmc9, RHSA-2018:2645, RHSA-2018:2776, RHSA-2018:2789, RHSA-2018:2790, SUSE-SU-2019:0955-1, SUSE-SU-2019:1425-1, SUSE-SU-2019:2230-1, UBUNTU-CVE-2018-5390, USN-3732-1, USN-3732-2 ## What is CVE-2018-5390? CVE-2018-5390 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 6 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Linux kernel versions 4.9+ can be forced to make very expensive calls to tcp_collapse_ofo_queue() and tcp_prune_ofo_queue() for every incoming packet which can lead to a denial of service. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2018-5390? It affects 38 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel-rt` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-debug` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-debug-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-debug-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-debuginfo-common-x86_64` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-doc` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-firmware` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-trace` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-trace-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-trace-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-vanilla` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-vanilla-debuginfo` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel-rt-vanilla-devel` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 1:3.10.0-693.39.1.rt56.629.el6rt | | `kernel` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-abi-whitelists` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debug` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debug-debuginfo` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debug-devel` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debuginfo` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-devel` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-doc` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-headers` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-tools` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-tools-debuginfo` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-tools-libs` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-tools-libs-devel` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `perf` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `perf-debuginfo` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `python-perf` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `python-perf-debuginfo` | Red Hat:rhel_aus:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-abi-whitelists` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debug` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debug-debuginfo` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debug-devel` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debuginfo` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_e4s:7.2::server | All versions | 0:3.10.0-327.73.1.el7 | Products: A10networks Advanced Core Operating System, Canonical Ubuntu Linux, Cisco Collaboration Meeting Rooms, Cisco Digital Network Architecture Center, Cisco Expressway, Cisco Expressway Series, Cisco Meeting Management, Cisco Network Assurance Engine, Cisco Telepresence Conductor Firmware, Cisco Telepresence Video Communication Server Firmware, Cisco Threat Grid-Cloud, Cisco Webex Hybrid Data Security, Cisco Webex Video Mesh, Debian Debian Linux, F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Domain Name System and 18 more. ## How do I fix CVE-2018-5390? Apply the vendor's patch. ## Is CVE-2018-5390 being exploited? There is no known exploitation of CVE-2018-5390 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-24384](https://insights.sbomify.com/CVE-2020-24384/): Code injection in n/a (critical 9.8) - [CVE-2023-42130](https://insights.sbomify.com/CVE-2023-42130/): A10 Thunder ADC FileMgmtExport Directory Traversal Arbitrary File Read and Deletion Vulnerability (high 8.3) - [CVE-2024-30369](https://insights.sbomify.com/CVE-2024-30369/): A10 Thunder ADC Incorrect Permission Assignment Local Privilege Escalation Vulnerability (high 7.8) - [CVE-2024-30368](https://insights.sbomify.com/CVE-2024-30368/): A10 Thunder ADC CsrRequestView Command Injection Remote Code Execution Vulnerability (high 7.2) - [CVE-2023-42129](https://insights.sbomify.com/CVE-2023-42129/): A10 Thunder ADC ShowTechDownloadView Directory Traversal Information Disclosure Vulnerability (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-5390 and fix it if it is affected. What it is: CVE-2018-5390 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 6 Aug 2018. 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-2018-5390 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-2018-5390/ (Markdown: https://insights.sbomify.com/CVE-2018-5390/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-5390 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-5390 - OSV: https://osv.dev/vulnerability/CVE-2018-5390 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-5390/ Summaries are generated and may contain mistakes; the official description above is the record.