# CVE-2014-0181: Missing authorization in n/a > Local attackers can bypass access restrictions and modify network configurations by exploiting Netlink socket authorization flaws in the Linux kernel. - **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`) - **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:** 27 Apr 2014 - **Updated:** 13 Feb 2025 - **Also known as:** DEBIAN-CVE-2014-0181, GHSA-759j-fmr2-pgj3, RHSA-2014:1959, UBUNTU-CVE-2014-0181 ## What is CVE-2014-0181? CVE-2014-0181 is a low-severity missing authorization vulnerability in Linux kernel, published on 27 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The Netlink implementation in the Linux kernel through 3.14.1 does not provide a mechanism for authorizing socket operations based on the opener of a socket, which allows local users to bypass intended access restrictions and modify network configurations by using a Netlink socket for the (1) stdout or (2) stderr of a setuid program. Weakness: CWE-264 ## Which versions are affected by CVE-2014-0181? It affects 7 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-PAE` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-PAE-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-debug` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-debug-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-doc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-headers` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-xen` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel-xen-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-400.el5 | | `kernel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-PAE` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-PAE-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-debug` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-debug-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-doc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-headers` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-kdump` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-kdump-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-kdump-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-xen` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | | `kernel-xen-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-400.el5 | Products: Linux kernel, Opensuse Evergreen, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Suse Linux Enterprise Real Time Extension, Suse Linux Enterprise Server, Suse Suse Linux Enterprise Server. ## How do I fix CVE-2014-0181? Apply the vendor's patch. ## Is CVE-2014-0181 being exploited? There is no known exploitation of CVE-2014-0181 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-2014-0181 and fix it if it is affected. What it is: CVE-2014-0181 is a low-severity missing authorization vulnerability in Linux kernel, published on 27 Apr 2014. 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-2014-0181 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-2014-0181/ (Markdown: https://insights.sbomify.com/CVE-2014-0181/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0181 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0181 - OSV: https://osv.dev/vulnerability/CVE-2014-0181 --- From sbomify Insights: https://insights.sbomify.com/CVE-2014-0181/ Summaries are generated and may contain mistakes; the official description above is the record.