kernel-packages team mailing list archive

Thread
Date

[Bug 1337339] Re: x86_64, ptrace: Enforce RIP <= TASK_SIZE_MAX (CVE-2014-4699)

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1337339@xxxxxxxxxxxxxxxxxx>
Date: Sat, 05 Jul 2014 16:42:57 -0000
Reply-to: Bug 1337339 <1337339@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package linux-lts-raring -
3.8.0-42.63~precise1

---------------
linux-lts-raring (3.8.0-42.63~precise1) precise; urgency=low

  [ Upstream Kernel Changes ]

  * x86_64,ptrace: Enforce RIP <= TASK_SIZE_MAX (CVE-2014-4699)
    - LP: #1337339
    - CVE-2014-4699
 -- Luis Henriques <luis.henriques@xxxxxxxxxxxxx>   Fri, 04 Jul 2014 10:14:37 +0100

** Changed in: linux-lts-saucy (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1337339

Title:
  x86_64,ptrace: Enforce RIP <= TASK_SIZE_MAX (CVE-2014-4699)

Status in “linux” package in Ubuntu:
  New
Status in “linux-armadaxp” package in Ubuntu:
  New
Status in “linux-ec2” package in Ubuntu:
  Fix Released
Status in “linux-fsl-imx51” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Fix Released
Status in “linux-lts-raring” package in Ubuntu:
  Fix Released
Status in “linux-lts-saucy” package in Ubuntu:
  Fix Released
Status in “linux-mvl-dove” package in Ubuntu:
  New
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux” source package in Lucid:
  New
Status in “linux” source package in Precise:
  Fix Released
Status in “linux” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  New
Status in “linux” source package in Utopic:
  New

Bug description:
  Don't allow ptrace to set RIP to a value that couldn't happen by
  ordinary control flow. There are CPU bugs^Wfeatures that can have
  interesting effects if RIP is non-canonical. I didn't make the
  corresponding x86_32 change, since x86_32 has no concept of canonical
  addresses. putreg32 doesn't need this fix: value is only 32 bits, so
  it can't be non-canonical.

  Break-Fix: 427abfa28afedffadfca9dd8b067eb6d36bac53f
  b9cd18de4db3c9ffa7e17b0dc0ca99ed5aa4d43a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337339/+subscriptions