This bug was fixed in the package linux - 2.6.32-42.95
--------------- linux (2.6.32-42.95) lucid-proposed; urgency=low
[Luis Henriques]
* Release Tracking Bug - LP: #1027831
[ Upstream Kernel Changes ]
* hugetlb: fix resv_map leak in error path - LP: #1004621 - CVE-2012-2390 * mm: fix vma_resv_map() NULL pointer - LP: #1004621 - CVE-2012-2390 * net: sock: validate data_len before allocating skb in sock_alloc_send_pskb() - LP: #1006622 - CVE-2012-2136 * 2.6.32.x: ntp: Fix leap-second hrtimer livelock - LP: #1020285 * 2.6.32.x: ntp: Correct TAI offset during leap second - LP: #1020285 * 2.6.32.x: timekeeping: Fix CLOCK_MONOTONIC inconsistency during leapsecond - LP: #1020285 * 2.6.32.x: time: Move common updates to a function - LP: #1020285 * 2.6.32.x: hrtimer: Provide clock_was_set_delayed() - LP: #1020285 * 2.6.32.x: timekeeping: Fix leapsecond triggered load spike issue - LP: #1020285 * 2.6.32.x: timekeeping: Maintain ktime_t based offsets for hrtimers - LP: #1020285 * 2.6.32.x: hrtimers: Move lock held region in hrtimer_interrupt() - LP: #1020285 * 2.6.32.x: timekeeping: Provide hrtimer update function - LP: #1020285 * 2.6.32.x: hrtimer: Update hrtimer base offsets each hrtimer_interrupt - LP: #1020285 * 2.6.32.x: timekeeping: Add missing update call in timekeeping_resume() - LP: #1020285 -- Luis Henriques <email address hidden> Tue, 24 Jul 2012 16:34:35 +0100
This bug was fixed in the package linux - 2.6.32-42.95
---------------
linux (2.6.32-42.95) lucid-proposed; urgency=low
[Luis Henriques]
* Release Tracking Bug
- LP: #1027831
[ Upstream Kernel Changes ]
* hugetlb: fix resv_map leak in error path alloc_send_ pskb() set_delayed( ) resume( )
- LP: #1004621
- CVE-2012-2390
* mm: fix vma_resv_map() NULL pointer
- LP: #1004621
- CVE-2012-2390
* net: sock: validate data_len before allocating skb in
sock_
- LP: #1006622
- CVE-2012-2136
* 2.6.32.x: ntp: Fix leap-second hrtimer livelock
- LP: #1020285
* 2.6.32.x: ntp: Correct TAI offset during leap second
- LP: #1020285
* 2.6.32.x: timekeeping: Fix CLOCK_MONOTONIC inconsistency during
leapsecond
- LP: #1020285
* 2.6.32.x: time: Move common updates to a function
- LP: #1020285
* 2.6.32.x: hrtimer: Provide clock_was_
- LP: #1020285
* 2.6.32.x: timekeeping: Fix leapsecond triggered load spike issue
- LP: #1020285
* 2.6.32.x: timekeeping: Maintain ktime_t based offsets for hrtimers
- LP: #1020285
* 2.6.32.x: hrtimers: Move lock held region in hrtimer_interrupt()
- LP: #1020285
* 2.6.32.x: timekeeping: Provide hrtimer update function
- LP: #1020285
* 2.6.32.x: hrtimer: Update hrtimer base offsets each hrtimer_interrupt
- LP: #1020285
* 2.6.32.x: timekeeping: Add missing update call in timekeeping_
- LP: #1020285
-- Luis Henriques <email address hidden> Tue, 24 Jul 2012 16:34:35 +0100