Candidate: CVE-2006-6058 References: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.23.y.git;a=commitdiff;h=f0ae3188daf70ed07a4dfbeb133bef3a92838a15 MISC:http://projects.info-pull.com/mokb/MOKB-17-11-2006.html FRSIRT:ADV-2006-4613 URL:http://www.frsirt.com/english/advisories/2006/4613 SECUNIA:23034 URL:http://secunia.com/advisories/23034 Description: The minix filesystem code in Linux kernel 2.6.x up to 2.6.18, and possibly other versions, allows local users to cause a denial of service (hang) via a malformed minix file stream that triggers an infinite loop in the minix_bmap function. NOTE: this issue might be due to an integer overflow or signedness error. Ubuntu-Description: The minix filesystem did not properly validate certain filesystem values. If a local attacker could trick the system into attempting to mount a corrupted minix filesystem, the kernel could be made to hang for long periods of time, resulting in a denial of service. Notes: dannf> ignored for sarge for now - only applies under very rare circumstances and don't know if there's an upstream fix jmm> We can ignore this, it has no practical ramifications dannf> Though I agree its minor, I suspect its not so rare that admins set user-mountable media's filesystem type to 'auto' in fstab, allowing them to use any fs on the system. I could see this being used to annoy sysadmins, e.g., in a university lab setting Bugs: upstream: released (2.6.23.7, 2.6.24-rc1) [f44ec6f3f89889a469773b1fd894f8fcc07c29cf] linux-2.6: released (2.6.23-1) [bugfix/2.6.23.7.patch] 2.6.18-etch-security: released (2.6.18.dfsg.1-13etch6) [bugfix/minixfs-printk-hang.patch] 2.6.8-sarge-security: released (2.6.8-17sarge1) [minixfs-printk-hang.dpatch] 2.4.27-sarge-security: ignored (2.4.27-10sarge6) "no printk_ratelimit in 2.4 - needs port" 2.6.15-dapper-security: released (2.6.15-29.61) 2.6.17-edgy-security: released (2.6.17.1-12.42) 2.6.20-feisty-security: released (2.6.20-16.33) 2.6.22-gutsy-security: released (2.6.22-14.47)