linux-kernel - [BUG 2.6.30_rc5] Null pointer dereference in rtc-cmos driver

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: <4A0C43C3.9090404@pardus.org.tr>
Date:	Thu, 14 May 2009 19:16:03 +0300
From:	Ozan Çağlayan <ozan@...dus.org.tr>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: [BUG 2.6.30_rc5] Null pointer dereference in rtc-cmos driver

Hi,

I don't know if the following scenario should be handled by kernel but
here's the steps to reproduce the problem:

1. Make rtc-cmos module built-in, compile the kernel and install it onto
system,
2. Keep the rtc-cmos.ko which is ABI compatible with the current kernel
in /lib/modules/* so that it could be probed by udev,
3. Reboot the system. Kernel synchronizes the system clock from hardware
clock as it could access /dev/rtc0,
4. Udev (141) starts, the default rule for rtc* is processed which then
tries to modprobe rtc-cmos.ko which is still available in /lib/modules,
5. rtc-cmos.ko ooopses, the keyboard is dead, etc.

dmesg output is attached.

Thanks,
Ozan Caglayan

View attachment "dmesg.log" of type "text/plain" (43023 bytes)