Skip to content
Noroxi
CVE-2005-0529· NVD / CVE Program· CNA redhat

Linux kernel 2.6.10 and 2.6.11rc1-bk6 uses different size types for offset arguments to the proc_file_read and locks_read_proc functions, wh

Linux kernel 2.6.10 and 2.6.11rc1-bk6 uses different size types for offset arguments to the proc_file_read and locks_read_proc functions, which leads to a heap-based buffer overflow when a signed comparison causes negative integers to be used in a positive context.

LowCVSS 2.1 · v2.0—No exploit Fix available
Published
May 2, 2005
Updated
Jun 16, 2026
EPSS
0.5% · 42th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

8

Monitor

Low priority for now.

CVSS
8 / 40 · 2.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

Affected systems

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.10
  • linux linux kernel2.6.11_rc1_bk6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:enterprise_linux:4::askernelbefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-debuginfobefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-develbefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-docbefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-hugemembefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-hugemem-develbefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-smpbefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL
Red Hat:enterprise_linux:4::askernel-smp-develbefore 0:2.6.9-5.0.5.EL0:2.6.9-5.0.5.EL

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:kernel0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-debuginfo0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-devel0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-doc0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-hugemem0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-hugemem-devel0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-smp0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:kernel-smp-devel0:2.6.9-5.0.5.EL · Red Hat:enterprise_linux:4::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

Weakness class (CWE)

—

CVSS vector

AV:L/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records