What is the severity of CVE-2005-2801?

CVE-2005-2801 has a moderate severity due to its potential impact on default ACLs in ext2 and ext3 file systems.

How do I fix CVE-2005-2801?

To fix CVE-2005-2801, you should upgrade the Linux kernel to a version later than 2.6.0 that addresses this vulnerability.

What systems are affected by CVE-2005-2801?

CVE-2005-2801 specifically affects Linux kernel version 2.6.0 running on ext2 and ext3 file systems.

What are the consequences of CVE-2005-2801?

The main consequence of CVE-2005-2801 is that it may prevent the proper application of default Access Control Lists (ACLs).

Is CVE-2005-2801 still a concern for current Linux distributions?

CVE-2005-2801 is not a concern for current Linux distributions as it has been resolved in later kernel updates.

Vulnerability/
CVE-2005-2801

high

7.5

CWE

NVD-CWE-Other 697

6/9/2005

7/8/2024

CVE-2005-2801

First published: Tue Sep 06 2005(Updated: )

xattr.c in the ext2 and ext3 file system code for Linux kernel 2.6 does not properly compare the name_index fields when sharing xattr blocks, which could prevent default ACLs from being applied.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Linux kernel	=2.6.0

Remedy

http://lists.debian.org/debian-kernel/2005/08/msg00238.html

Remedy

http://www.novell.com/linux/security/advisories/2005_18_kernel.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-2801?
CVE-2005-2801 has a moderate severity due to its potential impact on default ACLs in ext2 and ext3 file systems.
How do I fix CVE-2005-2801?
To fix CVE-2005-2801, you should upgrade the Linux kernel to a version later than 2.6.0 that addresses this vulnerability.
What systems are affected by CVE-2005-2801?
CVE-2005-2801 specifically affects Linux kernel version 2.6.0 running on ext2 and ext3 file systems.
What are the consequences of CVE-2005-2801?
The main consequence of CVE-2005-2801 is that it may prevent the proper application of default Access Control Lists (ACLs).
Is CVE-2005-2801 still a concern for current Linux distributions?
CVE-2005-2801 is not a concern for current Linux distributions as it has been resolved in later kernel updates.

agent/references
agent/type
agent/remedy
agent/softwarecombine
agent/weakness
agent/severity
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
collector/nvd-historical
vendor/linux
canonical/linux kernel
version/linux kernel/2.6.0

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2005-2801?
CVE-2005-2801 has a moderate severity due to its potential impact on default ACLs in ext2 and ext3 file systems.
How do I fix CVE-2005-2801?
To fix CVE-2005-2801, you should upgrade the Linux kernel to a version later than 2.6.0 that addresses this vulnerability.
What systems are affected by CVE-2005-2801?
CVE-2005-2801 specifically affects Linux kernel version 2.6.0 running on ext2 and ext3 file systems.
What are the consequences of CVE-2005-2801?
The main consequence of CVE-2005-2801 is that it may prevent the proper application of default Access Control Lists (ACLs).
Is CVE-2005-2801 still a concern for current Linux distributions?
CVE-2005-2801 is not a concern for current Linux distributions as it has been resolved in later kernel updates.