This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 439999 - (CVE-2007-6712) CVE-2007-6712 kernel: infinite loop in highres timers (kernel hang)
CVE-2007-6712 kernel: infinite loop in highres timers (kernel hang)
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 440001 440002 453136
  Show dependency treegraph
Reported: 2008-04-01 06:04 EDT by Jan Lieskovsky
Modified: 2016-03-04 07:00 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-22 18:47:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Testcase to reproduce the kernel hang (3.51 KB, text/x-csrc)
2008-04-01 06:09 EDT, Jan Lieskovsky
no flags Details

  None (edit)
Description Jan Lieskovsky 2008-04-01 06:04:53 EDT
Description of problem:

Thomas Glexner has provided patch for the following kernel issue:

hrtimer_forward() does not check for the possible overflow of
timer->expires.  This can happen on 64 bit machines with large interval
values and results currently in an endless loop in the softirq because the
expiry value becomes negative and therefor the timer is expired all the

Check for this condition and set the expiry value to the max.  expiry time
in the future.  The fix should be applied to stable kernel series as well.

Steps to reproduce:  See the next comment for the reproducer.

Actual result:    Kernel hang.

Expected result:  No kernel hang.


Proposed patch from Thomas:;a=commitdiff;h=13788ccc41ceea5893f9c747c59bc0b28f2416c2
Comment 9 Vincent Danen 2010-12-22 18:47:25 EST
This was addressed via:

Red Hat Enterprise Linux version 5 (RHSA-2008:0275)
MRG Realtime for RHEL 5 Server (RHSA-2008:0585)

Note You need to log in before you can comment on or make changes to this bug.