CVE-2005-0757: The xattr file system code, as backported in Red Hat Enterprise Linux 3 on 64-bit systems, does not properly handle certain offsets, which…
Noroxi assessment
Priority: Monitor (action score 8/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: kernel-image-2.4.27-alpha (Debian:3.1) 2.4.27-10sarge1; kernel-image-2.4.27-arm (Debian:3.1) 2.4.27-2sarge1; kernel-image-2.4.27-i386 (Debian:3.1) 2.4.27-10sarge1.
Low priority for now. Upgrade to kernel-image-2.4.27-alpha (Debian:3.1) 2.4.27-10sarge1; kernel-image-2.4.27-arm (Debian:3.1) 2.4.27-2sarge1; kernel-image-2.4.27-i386 (Debian:3.1) 2.4.27-10sarge1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The xattr file system code, as backported in Red Hat Enterprise Linux 3 on 64-bit systems, does not properly handle certain offsets, which allows local users to cause a denial of service (system crash) via certain actions on an ext3 file system with extended attributes enabled.
- Published
- May 18, 2005
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- —
Report tools
Action score
8
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat enterprise linux3.0
- redhat enterprise linux desktop3.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:3.1 | kernel-image-2.4.27-alpha | before 2.4.27-10sarge1 | 2.4.27-10sarge1 |
| Debian:3.1 | kernel-image-2.4.27-arm | before 2.4.27-2sarge1 | 2.4.27-2sarge1 |
| Debian:3.1 | kernel-image-2.4.27-i386 | before 2.4.27-10sarge1 | 2.4.27-10sarge1 |
| Debian:3.1 | kernel-image-2.4.27-ia64 | before 2.4.27-10sarge1 | 2.4.27-10sarge1 |
| Debian:3.1 | kernel-image-2.4.27-m68k | before 2.4.27-3sarge1 | 2.4.27-3sarge1 |
| Debian:3.1 | kernel-image-2.4.27-s390 | before 2.4.27-2sarge1 | 2.4.27-2sarge1 |
| Debian:3.1 | kernel-image-2.4.27-sparc | before 2.4.27-9sarge1 | 2.4.27-9sarge1 |
| Debian:3.1 | kernel-image-2.6.8-alpha | before 2.6.8-16sarge1 | 2.6.8-16sarge1 |
| Debian:3.1 | kernel-image-2.6.8-amd64 | before 2.6.8-16sarge1 | 2.6.8-16sarge1 |
| Debian:3.1 | kernel-image-2.6.8-hppa | before 2.6.8-6sarge1 | 2.6.8-6sarge1 |
| Debian:3.1 | kernel-image-2.6.8-i386 | before 2.6.8-16sarge1 | 2.6.8-16sarge1 |
| Debian:3.1 | kernel-image-2.6.8-ia64 | before 2.6.8-14sarge1 | 2.6.8-14sarge1 |
| Debian:3.1 | kernel-image-2.6.8-m68k | before 2.6.8-4sarge1 | 2.6.8-4sarge1 |
| Debian:3.1 | kernel-image-2.6.8-s390 | before 2.6.8-5sarge1 | 2.6.8-5sarge1 |
| Debian:3.1 | kernel-image-2.6.8-sparc | before 2.6.8-15sarge1 | 2.6.8-15sarge1 |
| Debian:3.1 | kernel-patch-2.4.27-arm | before 2.4.27-1sarge1 | 2.4.27-1sarge1 |
| Debian:3.1 | kernel-patch-2.4.27-mips | before 2.4.27-10.sarge1.040815-1 | 2.4.27-10.sarge1.040815-1 |
| Debian:3.1 | kernel-patch-powerpc-2.4.27 | before 2.4.27-10sarge1 | 2.4.27-10sarge1 |
| Debian:3.1 | kernel-patch-powerpc-2.6.8 | before 2.6.8-12sarge1 | 2.6.8-12sarge1 |
| Debian:3.1 | kernel-source-2.4.27 | before 2.4.27-10sarge1 | 2.4.27-10sarge1 |
| Debian:3.1 | kernel-source-2.6.8 | before 2.6.8-16sarge1 | 2.6.8-16sarge1 |
| Red Hat:enterprise_linux:3::as | kernel | before 0:2.4.21-32.EL | 0:2.4.21-32.EL |
| Red Hat:enterprise_linux:3::as | kernel-BOOT | before 0:2.4.21-32.EL | 0:2.4.21-32.EL |
| Red Hat:enterprise_linux:3::as | kernel-debuginfo | before 0:2.4.21-32.EL | 0:2.4.21-32.EL |
+7
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-3246libuser before 0.56.13-8 and 0.60 before 0.60-7, as used in the userhelper program in the usermode package, directly modifies /etc/passwd…KEV62This week
- CVE-2023-50387Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of…60This week
- CVE-2017-5456A mechanism to bypass file system access protections in the sandbox using the file system request constructor through an IPC message.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2005-0091May 2, 2005 · Unknown vulnerability in the Red Hat Enterprise Linux 4 kernel 4GB/4GB split patch, when using the hugemem kernel, allows local users to…28Monitor
- ← EarlierCVE-2005-1194May 4, 2005 · Stack-based buffer overflow in the ieee_putascii function for nasm 0.98 and earlier allows attackers to execute arbitrary code via a…18Monitor
- Later →CVE-2005-0403Sep 1, 2005 · init_dev in tty_io.c in the Red Hat backport of NPTL to Red Hat Enterprise Linux 3 does not properly clear controlling tty's in…28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:kernel-image-2.4.27-alpha | 2.4.27-10sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-image-2.4.27-arm | 2.4.27-2sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-image-2.4.27-i386 | 2.4.27-10sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-image-2.4.27-ia64 | 2.4.27-10sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-image-2.4.27-m68k | 2.4.27-3sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-image-2.4.27-s390 | 2.4.27-2sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-image-2.4.27-sparc | 2.4.27-9sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-patch-2.4.27-arm | 2.4.27-1sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-patch-2.4.27-mips | 2.4.27-10.sarge1.040815-1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-patch-powerpc-2.4.27 | 2.4.27-10sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-source-2.4.27 | 2.4.27-10sarge1 · Debian:3.1 | Package registry (OSV) |
| debian:kernel-source-2.6.8 | 2.6.8-16sarge1 · Debian:3.1 | Package registry (OSV) |
| red hat:kernel | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-BOOT | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-doc | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-hugemem | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-hugemem-unsupported | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-smp | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-smp-unsupported | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-source | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:kernel-unsupported | 0:2.4.21-32.EL · Red Hat:enterprise_linux:3::as | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
—
CVSS vector
AV:L/AC:L/Au:N/C:N/I:N/A:P
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.