linux-kernel - Q: a bogus set_fs(USER_DS) in setup_frame/setup_rt

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-next>] [day] [month] [year] [list]

Message-ID: <20070717154638.GA342@tv-sign.ru>
Date:	Tue, 17 Jul 2007 19:46:38 +0400
From:	Oleg Nesterov <oleg@...sign.ru>
To:	Chuck Ebbert <76306.1226@...puserve.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Roland McGrath <roland@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Q: a bogus set_fs(USER_DS) in setup_frame/setup_rt_frame ?

I am really puzzled by set_fs(USER_DS) in setup_frame/setup_rt_frame.

How is it possible that current->addr_limit != USER_DS ? If this _is_
possible, how can can we trust the result of access_ok() above?

Thanks in advance,

Oleg.

-
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/