linux-kernel - Re: Redzone overwritten with CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 31 May 2008 16:24:03 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Eric Sesterhenn <snakebyte@....de>
Cc:	Chris Wright <chrisw@...s-sol.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, James Morris <jmorris@...ei.org>,
	William Lee Irwin III <wli@...omorphy.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: Redzone overwritten with CONFIG_SECURITY

* Chris Wright (chrisw@...s-sol.org) wrote:
> * Eric Sesterhenn (snakebyte@....de) wrote:
> > Is it possible that this was caused because a file didnt
> > get rebuild correctly? I can still reproduce it with the
> > old checkout. Sorry if this causes unessecary noise :(
> 
> I had wondered that, since data structures will grow w/ CONFIG_SECURITY
> set (like inode, for example).  I haven't encountered a Kbuild dependency
> bug in quite a while though.

Yeah, this thing is miscompiled (thanks for the vmlinux).

$ cd /tmp/CONFIG_SECURITY-mem-corruption
$ gdb -q vmlinux
(gdb) p sizeof(struct inode)
$1 = 596
(gdb) p sizeof(struct hugetlbfs_inode_info)
$2 = 592

struct hugetlbfs_inode_info {
	struct shared_policy policy;
	struct inode vfs_inode;
};
 
The hugetlbfs_inode_info structure isn't updated with the 4 extra bytes
added from CONFIG_SECURITY to struct inode.

If you're interested in more gory details, you can look at:
$ eu-readelf -winfo vmlinux > readelf-info.out

thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/