The flaw, found by two software programmers, could give a user with access to a Linux system the ability to crash the system using two dozen lines of code written in the C programming language, said an advisory posted over the weekend on linuxreviews.
"Assume your kernel is (vulnerable) unless you have good reason to believe it is safe," Oyvind Saether, one of the discoverers of the flaw, said in the advisory.
The program, dubbed "evil.c," causes problems with the code sent to the floating-point unit, the part of the processor that handles noninteger calculations, according to a note in a source code patch published by Linux founder Linus Torvalds.
The open-source Linux operating system has fallen prey to its share of flaws and attacks this year. Several flaws were found in the Concurrent Versions System, CVS, a commonly used application for managing open-source code under development. In March and April, online attackers targeted Linux and Solaris systems at many academic high-performance computing centers.
Researchers also found flaws in the OpenSSL software used by many Linux distributions to enable secure Internet communications.
On Monday, staffers associated with Red Hat's community-based distribution, Fedora, released an update to Fedora Core 2, to fix the latest problem. The kernel patch has also been included in the latest release candidate of the Linux kernel, 2.6.7-RC3, which is expected to be released soon.
Other distributions of Linux should be fixed this week as well.
Andrew Morton, the maintainer of the Linux 2.6 kernel, promised a fix within 48 hours and said the flaw was not very serious.
"Bugs wherein local users can lock the machine up are not uncommon, and local users have always been able to bring a machine to its knees anyway--say, by using up all the memory," he said.
Morton said the discoverers of the flaw didn't give the kernel team any notice before releasing the code to take advantage of the problem--a no-no in the security community.
The Linux Way.
"Bugs wherein local users can lock the machine up are not uncommon, and local users have always been able to bring a machine to its knees anyway--say, by using up all the memory," he said.
The FreeBSD Way.
(from the man pages)
"A login class (an optional annotation against each record in the user account database, /etc/master.passwd) determines session accounting, resource limits and user environment settings."
i.e. a user cannot disable the machine through malice, stupidity, or bad luck - once the admin has set limits (global and user specific) on resources that a user may acquire.