cve.bz

CVE-2010-1437 Race Condition

7.0 highExploitEPSS 0.7%Fix available

High (7.0). EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
CWE-416 Use After Free
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2010-1437 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2010-1437?via=ask-ai-copy and https://cve.bz/cve/CVE-2010-1437?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2010-1437 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linux:linux_kernelbefore 2.6.34
linux:linux_kernel2.6.34:rc1
linux:linux_kernel2.6.34:rc2
linux:linux_kernel2.6.34:rc3
linux:linux_kernel2.6.34:rc4
linux:linux_kernel2.6.34:rc5
opensuse:opensuse11.1
suse:linux_enterprise_desktop11
suse:linux_enterprise_high_availability_extension11
suse:linux_enterprise_server11
debian:debian_linux5.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian5.0linux-2.62.6.26-22lenny1DSA-2053-1
Red Hatenterprise_linux:4::as, enterprise_linux:4::desktop, enterprise_linux:4::es and 1 morekernel, kernel-doc, kernel-smp and 9 more0:2.6.9-89.0.26.ELRHSA-2010:0474
Red Hatenterprise_linux:5::clientkernel, kernel-PAE, kernel-doc and 11 more0:2.6.18-194.8.1.el5RHSA-2010:0504
Red Hatenterprise_linux:5::serverkernel, kernel-PAE, kernel-doc and 14 more0:2.6.18-194.8.1.el5RHSA-2010:0504
Red Hatenterprise_mrg:1::el5kernel-rt, kernel-rt-doc, kernel-rt-debug and 12 more0:2.6.24.7-161.el5rtRHSA-2010:0631

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This issue did not affect the version of Linux kernel as shipped with Red Hat

Enterprise Linux 3. Future kernel updates in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG will address this issue.

ProductPackageStateAdvisory
MRG for RHEL-5kernel-rt-0:2.6.24.7-161.el5rtFixed 2010-08-17RHSA-2010:0631
Red Hat Enterprise Linux 4kernel-0:2.6.9-89.0.26.ELFixed 2010-06-15RHSA-2010:0474
Red Hat Enterprise Linux 5kernel-0:2.6.18-194.8.1.el5Fixed 2010-07-01RHSA-2010:0504

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2010-1437.

Public exploits

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON