CVE-2010-4347: Medium severity linux kernel vulnerability
Reported by Dave Jones, currently we have:
--w--w--w-. 1 root root 0 2010-11-11 14:56 /sys/kernel/debug/acpi/custommethod
which is just crazy. Change this to --w-------.
This custommethod file allows to inject custom ACPI methods into the ACPI interpreter tables. This control file was introduced with world writeable permissions in Linux Kernel 2.6.33.
Introduced in: http://git.kernel.org/linus/a1a541d86f50a9957beeedb122a035870d602647 http://git.kernel.org/linus/a25ee9200eef07377e1703697afbb5d81f89e500
Fixed in: http://git.kernel.org/linus/ed3aada1bf34c5a9e98af167f125f8a740fc726a
Other sources
The ACPI subsystem in the Linux kernel before 2.6.36.2 uses 0222 permissions for the debugfs custommethod file, which allows local users to gain privileges by placing a custom ACPI method in the ACPI interpreter tables, related to the acpidebugfsinit function in drivers/acpi/debugfs.c.
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-4347?
CVE-2010-4347 has been classified as a high severity vulnerability due to its potential to allow unauthorized access to critical system functions.
How do I fix CVE-2010-4347?
To fix CVE-2010-4347, update the kernel to version 2.6.36.2 or later, or apply the necessary patches as recommended by your distribution.
What are the potential impacts of CVE-2010-4347?
The potential impacts of CVE-2010-4347 include privilege escalation and the ability for attackers to execute arbitrary code through custom ACPI methods.
Which systems are affected by CVE-2010-4347?
CVE-2010-4347 affects several distributions including Red Hat Enterprise Linux, openSUSE 11.3, and SUSE Linux Enterprise Real Time Extension 11 SP1.
Is there a workaround for CVE-2010-4347?
A temporary workaround for CVE-2010-4347 may include changing the permissions of the /sys/kernel/debug/acpi/custom_method file to restrict access.