Bug 617903 (CVE-2010-2243) - VUL-1: CVE-2010-2243: kernel: GENERIC_TIME=n issue
Summary: VUL-1: CVE-2010-2243: kernel: GENERIC_TIME=n issue
Status: RESOLVED INVALID
Alias: CVE-2010-2243
Product: SUSE Security Incidents
Classification: Novell Products
Component: General (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL:
Whiteboard: CVSSv2:NVD:CVE-2010-2243:7.8:(AV:N/A...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-28 13:00 UTC by Marcus Meissner
Modified: 2019-11-09 08:11 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2010-06-28 13:00:50 UTC 
is public, from oss-sec:

Please use CVE-2010-2243 for this.

Thanks.

----- "Eugene Teo" <eugeneteo@kernel.sg> wrote:

> "Aaro Koskinen reported an issue in kernel.org 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:
> http://git.kernel.org/linus/ad6759fbf35d104dbf573cd6f4c6784ad6823f7e
> 
> I believe distros are using GENERIC_TIME=y, at least this is the case
> in 
> our supported kernels.
> 
> Thanks, Eugene
Comment 1 Marcus Meissner 2010-06-28 13:30:37 UTC 
as far as I can see, we always have GENERIC_TIME=y. _> not affected