# CVE-2010-1437: Race condition in n/a

> Local attackers can trigger a race condition in the Linux kernel keyring subsystem to cause memory corruption and system crashes.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mrjp-428h-53c5

## What is CVE-2010-1437?

CVE-2010-1437 is a high-severity vulnerability in Debian Debian Linux, published on 7 May 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in the find_keyring_by_name function in security/keys/keyring.c in the Linux kernel 2.6.34-rc5 and earlier allows local users to cause a denial of service (memory corruption and system crash) or possibly have unspecified other impact via keyctl session commands that trigger access to a dead keyring that is undergoing deletion by the key_cleanup function.

Weakness: CWE-416 (Use After Free), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2010-1437?

It affects 6 products.


Products: Debian Debian Linux, Linux kernel, Opensuse Opensuse, Suse Linux Enterprise Desktop, Suse Linux Enterprise High Availability Extension, Suse Linux Enterprise Server.

## How do I fix CVE-2010-1437?

Apply the vendor's patch.

## Is CVE-2010-1437 being exploited?

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

Public exploit code:

- Linux Kernel 2.6.34 - 'find_keyring_by_name()' Local Memory Corruption (exploitdb)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1437 and fix it if it is affected.

What it is: CVE-2010-1437 is a high-severity vulnerability in Debian Debian Linux, published on 7 May 2010. 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-2010-1437 exists.

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

## Sources

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

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