CVE-2004-0535: Buffer Overflow

Published Jun 8, 2004
·
Updated

The e1000 driver for Linux kernel 2.4.26 and earlier does not properly initialize memory before using it, which allows local users to read portions of kernel memory. NOTE: this issue was originally incorrectly reported as a "buffer overflow" by some sources.

Affected Software

93 affected components
Mandrakesoft Mandrake Multi Network Firewall=8.2
SUSE Suse Email Server=3.1
SUSE Suse Email Server=iii
SUSE Suse Linux Admin-cd For Firewall
SUSE Suse Linux Connectivity Server
SUSE Suse Linux Database Server
SUSE Suse Linux Firewall Cd
SUSE Suse Linux Firewall Live-cd
SUSE Suse Linux Office Server
SUSE Suse Office Server
Conectiva Linux=8.0
Conectiva Linux=9.0
Engardelinux Secure Community=2.0
Engardelinux Secure Linux=1.5
Gentoo Linux=1.4
Linux Linux kernel=2.4.0
Linux Linux kernel=2.4.0-test1
Linux Linux kernel=2.4.0-test10
Linux Linux kernel=2.4.0-test11
Linux Linux kernel=2.4.0-test12
Linux Linux kernel=2.4.0-test2
Linux Linux kernel=2.4.0-test3
Linux Linux kernel=2.4.0-test4
Linux Linux kernel=2.4.0-test5
Linux Linux kernel=2.4.0-test6
Linux Linux kernel=2.4.0-test7
Linux Linux kernel=2.4.0-test8
Linux Linux kernel=2.4.0-test9
Linux Linux kernel=2.4.1
Linux Linux kernel=2.4.2
Linux Linux kernel=2.4.3
Linux Linux kernel=2.4.4
Linux Linux kernel=2.4.5
Linux Linux kernel=2.4.6
Linux Linux kernel=2.4.7
Linux Linux kernel=2.4.8
Linux Linux kernel=2.4.9
Linux Linux kernel=2.4.10
Linux Linux kernel=2.4.11
Linux Linux kernel=2.4.12
Linux Linux kernel=2.4.13
Linux Linux kernel=2.4.14
Linux Linux kernel=2.4.15
Linux Linux kernel=2.4.16
Linux Linux kernel=2.4.17
Linux Linux kernel=2.4.18
Linux Linux kernel=2.4.18
Linux Linux kernel=2.4.18-pre1
Linux Linux kernel=2.4.18-pre2
Linux Linux kernel=2.4.18-pre3
Linux Linux kernel=2.4.18-pre4
Linux Linux kernel=2.4.18-pre5
Linux Linux kernel=2.4.18-pre6
Linux Linux kernel=2.4.18-pre7
Linux Linux kernel=2.4.18-pre8
Linux Linux kernel=2.4.19
Linux Linux kernel=2.4.19-pre1
Linux Linux kernel=2.4.19-pre2
Linux Linux kernel=2.4.19-pre3
Linux Linux kernel=2.4.19-pre4
Linux Linux kernel=2.4.19-pre5
Linux Linux kernel=2.4.19-pre6
Linux Linux kernel=2.4.20
Linux Linux kernel=2.4.21
Linux Linux kernel=2.4.21-pre1
Linux Linux kernel=2.4.21-pre4
Linux Linux kernel=2.4.21-pre7
Linux Linux kernel=2.4.22
Linux Linux kernel=2.4.23
Linux Linux kernel=2.4.23-pre9
Linux Linux kernel=2.4.23_ow2
Linux Linux kernel=2.4.24
Linux Linux kernel=2.4.24_ow1
Linux Linux kernel=2.4.25
Linux Linux kernel=2.4.26
Linux Linux kernel=2.4.27-pre1
Mandrakesoft Mandrake Linux=9.1
Mandrakesoft Mandrake Linux=9.1
Mandrakesoft Mandrake Linux=9.2
Mandrakesoft Mandrake Linux=9.2
Mandrakesoft Mandrake Linux=10.0
Mandrakesoft Mandrake Linux=10.0
Mandrakesoft Mandrake Linux Corporate Server=2.1
Mandrakesoft Mandrake Linux Corporate Server=2.1
SUSE SuSE Linux=7
SUSE SuSE Linux=8
SUSE SuSE Linux=8.0
SUSE SuSE Linux=8.0
SUSE SuSE Linux=8.1
SUSE SuSE Linux=8.2
SUSE SuSE Linux=9.0
SUSE SuSE Linux=9.0
SUSE SuSE Linux=9.1

Event History

Jun 8, 2004
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2004-0535?

CVE-2004-0535 is classified as a medium severity vulnerability due to the potential for local users to read sensitive kernel memory.

2

How do I fix CVE-2004-0535?

To fix CVE-2004-0535, upgrade to a later version of the Linux kernel that properly initializes memory.

3

What systems are affected by CVE-2004-0535?

CVE-2004-0535 affects Linux kernel versions 2.4.26 and earlier, particularly in distributions like Conectiva Linux, SUSE Linux, and Mandrake Linux.

4

Can CVE-2004-0535 be exploited remotely?

CVE-2004-0535 cannot be exploited remotely as it requires local access to the vulnerable system.

5

What is the nature of the issue in CVE-2004-0535?

CVE-2004-0535 is due to the e1000 driver not properly initializing memory, allowing local users to access portions of kernel memory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203