# CVE-2005-1767: Denial of service in n/a

> Local users can trigger a denial of service in the Linux kernel by causing stack segment faults on the exception stack.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 5 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5wx4-mvjj-533c

## What is CVE-2005-1767?

CVE-2005-1767 is a low-severity denial of service vulnerability in Suse Suse Linux, published on 5 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

traps.c in the Linux kernel 2.6.x and 2.4.x executes stack segment faults on an exception stack, which allows local users to cause a denial of service (oops and stack fault exception).

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

It affects 3 products.


Products: Novell Linux Desktop, Novell Open Enterprise Server, Suse Suse Linux.

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

Apply the vendor's patch.

## Is CVE-2005-1767 being exploited?

There is no known exploitation of CVE-2005-1767 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-1763](https://insights.sbomify.com/CVE-2005-1763/): Memory corruption in n/a (high 7.2)
- [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-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-1767 and fix it if it is affected.

What it is: CVE-2005-1767 is a low-severity denial of service vulnerability in Suse Suse Linux, published on 5 Aug 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-1767 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-1767/ (Markdown: https://insights.sbomify.com/CVE-2005-1767/index.md)
```

## Sources

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

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