# CVE-2005-1763: Memory corruption in n/a

> Local attackers can exploit a buffer overflow in the Linux kernel ptrace to write to kernel memory, potentially gaining elevated privileges.

- **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:** 14 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8q3q-7x3w-xq6g

## What is CVE-2005-1763?

CVE-2005-1763 is a high-severity memory corruption vulnerability in Suse Suse Linux, published on 14 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in ptrace in the Linux Kernel for 64-bit architectures allows local users to write bytes into kernel memory.

## Which versions are affected by CVE-2005-1763?

It affects 2 products.


Products: Novell Linux Desktop, Suse Suse Linux.

## How do I fix CVE-2005-1763?

Apply the vendor's patch.

## Is CVE-2005-1763 being exploited?

There is no known exploitation of CVE-2005-1763 in the wild and no public exploit code.

## Other vulnerabilities in Suse Suse Linux

- [CVE-2006-0736](https://insights.sbomify.com/CVE-2006-0736/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-1040](https://insights.sbomify.com/CVE-2005-1040/): Privilege escalation in n/a (high 7.2)
- [CVE-2005-1761](https://insights.sbomify.com/CVE-2005-1761/): Denial of service in n/a (low 2.1)
- [CVE-2005-1767](https://insights.sbomify.com/CVE-2005-1767/): Denial of service in n/a (low 2.1)
- [CVE-2005-1065](https://insights.sbomify.com/CVE-2005-1065/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1763 and fix it if it is affected.

What it is: CVE-2005-1763 is a high-severity memory corruption vulnerability in Suse Suse Linux, published on 14 Jun 2005. 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-2005-1763 in the wild and no public exploit code.

Affected product: Suse Suse 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-2005-1763/ (Markdown: https://insights.sbomify.com/CVE-2005-1763/index.md)
```

## Sources

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

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