linux-kernel - Re: [PATCH -tip] kmemcheck: fix crash in PnP BIOS calls

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]

Message-ID: <20081005201056.5b9b2f53@lxorguk.ukuu.org.uk>
Date:	Sun, 5 Oct 2008 20:10:56 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Vegard Nossum" <vegard.nossum@...il.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Pekka Enberg" <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -tip] kmemcheck: fix crash in PnP BIOS calls

> catch those reads/writes just fine. I'm not sure if the BIOS code can
> change segments (it would need to switch LDT/GDTs, I think), and even

It can do so if it wants as far as I can tell

> if it did, I find it unlikely that it would directly access kernel
> memory using these new segment registers. Do you happen to know of any
> such cases?

No. The code either seems to be very simple or just be an SMM trap in the
BIOSes I've seen
--
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/