# CVE-2003-0127: Privilege escalation in n/a

> Local attackers can gain root privileges by attaching to kernel-spawned child processes via ptrace in vulnerable Linux kernels.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-270, DSA-276, GHSA-jhjp-mfjv-rvhx

## What is CVE-2003-0127?

CVE-2003-0127 is a high-severity vulnerability in Linux kernel, published on 18 Mar 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The kernel module loader in Linux kernel 2.2.x before 2.2.25, and 2.4.x before 2.4.21, allows local users to gain root privileges by using ptrace to attach to a child process that is spawned by the kernel.

## Which versions are affected by CVE-2003-0127?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2003-0127?

Upgrade to a fixed version.

## Is CVE-2003-0127 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0127 exists.

Public exploit code:

- Secured root-level access by identifying and exploiting misconfigurations and outdated software. Buffer overflow vulnerability in an outdated version of mod_ssl (CVE-2002-0082). Privilege escalation was subsequently achieved by exploiting a race condition in the Linux kernel's "ptrace" utility (CVE-2003-0127), (github_poc): https://github.com/anilkashyap01/Binary-Exploitation-and-Kernel-Escalation
- Linux Kernel 2.2.x/2.4.x - Privileged Process Hijacking Privilege Escalation (1) (exploitdb)
- Linux Kernel 2.2.x/2.4.x (RedHat) - 'ptrace/kmod' Local Privilege Escalation (exploitdb)
- Linux Kernel 2.2.x/2.4.x - Privileged Process Hijacking Privilege Escalation (2) (exploitdb)
- Linux Kernel < 2.4.20 - Module Loader Privilege Escalation (exploitdb)

## 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-2003-0127 and fix it if it is affected.

What it is: CVE-2003-0127 is a high-severity vulnerability in Linux kernel, published on 18 Mar 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0127 exists.

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-2003-0127/ (Markdown: https://insights.sbomify.com/CVE-2003-0127/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2003-0127
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2003-0127
- OSV: https://osv.dev/vulnerability/CVE-2003-0127

---
From sbomify Insights: https://insights.sbomify.com/CVE-2003-0127/
Summaries are generated and may contain mistakes; the official description above is the record.