This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
--------------- linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug - LP: #1326748 * Rebase to Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1) - LP: #1326367 - CVE-2014-3153 * futex: Validate atomic acquisition in futex_lock_pi_atomic() - LP: #1326367 - CVE-2014-3153 * futex: Always cleanup owner tid in unlock_pi - LP: #1326367 - CVE-2014-3153 * futex: Make lookup_pi_state more robust - LP: #1326367 - CVE-2014-3153 -- Ike Panhc <email address hidden> Thu, 05 Jun 2014 19:41:05 +0800
This bug was fixed in the package linux-armadaxp - 3.2.0-1634.49
---------------
linux-armadaxp (3.2.0-1634.49) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1326748
* Rebase to Ubuntu-3.2.0-64.97
[ Ubuntu: 3.2.0-64.97 ]
* futex-prevent- requeue- pi-on-same- futex.patch futex: Forbid uaddr == pi_atomic( )
uaddr2 in futex_requeue(..., requeue_pi=1)
- LP: #1326367
- CVE-2014-3153
* futex: Validate atomic acquisition in futex_lock_
- LP: #1326367
- CVE-2014-3153
* futex: Always cleanup owner tid in unlock_pi
- LP: #1326367
- CVE-2014-3153
* futex: Make lookup_pi_state more robust
- LP: #1326367
- CVE-2014-3153
-- Ike Panhc <email address hidden> Thu, 05 Jun 2014 19:41:05 +0800