Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 23 Jun 2010 10:50:04 +0800
From: Eugene Teo <>
CC: "Steven M. Christey" <>
Subject: CVE request: kernel: timekeeping: Prevent oops when GENERIC_TIME=n

"Aaro Koskinen reported an issue in bugzilla #15366, where on 
non-GENERIC_TIME systems, accessing 
/sys/devices/system/clocksource/clocksource0/current_clocksource results 
in an oops.

It seems the timekeeper/clocksource rework missed initializing the 
curr_clocksource value in the !GENERIC_TIME case."

Upstream commit:

I believe distros are using GENERIC_TIME=y, at least this is the case in 
our supported kernels.

Thanks, Eugene
main(i) { putchar(182623909 >> (i-1) * 5&31|!!(i<7)<<6) && main(++i); }

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.