kernel-packages team mailing list archive

Thread
Date
[Bug 1097680] Re: CVE-2013-0160

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: John Johansen <john.johansen@xxxxxxxxxxxxx>
Date: Thu, 30 Jan 2014 21:01:22 -0000
Reply-to: Bug 1097680 <1097680@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
** Changed in: linux-armadaxp (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-armadaxp (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-armadaxp (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-armadaxp (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-ec2 (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-ec2 (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-ec2 (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-ec2 (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-ec2 (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-lts-quantal (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-lts-quantal (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-lts-quantal (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-mvl-dove (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-mvl-dove (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-mvl-dove (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-mvl-dove (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-mvl-dove (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-lts-saucy (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-lts-saucy (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-lts-saucy (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-ti-omap4 (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-ti-omap4 (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-ti-omap4 (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-fsl-imx51 (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-fsl-imx51 (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-fsl-imx51 (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-fsl-imx51 (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-fsl-imx51 (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-lts-raring (Ubuntu Precise)
   Importance: Low => Critical

** Changed in: linux-lts-raring (Ubuntu Saucy)
   Importance: Low => Critical

** Changed in: linux-lts-raring (Ubuntu Lucid)
   Importance: Low => Critical

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Importance: Low => Critical

** Changed in: linux-lts-raring (Ubuntu Quantal)
   Importance: Low => Critical

** Changed in: linux-armadaxp (Ubuntu Precise)
       Status: Fix Released => New

** Changed in: linux-armadaxp (Ubuntu Quantal)
       Status: Fix Released => New

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

** Changed in: linux (Ubuntu Precise)
       Status: Fix Released => New

** Changed in: linux (Ubuntu Saucy)
       Status: Fix Released => New

** Changed in: linux (Ubuntu Trusty)
       Status: Fix Released => New

** Changed in: linux (Ubuntu Quantal)
       Status: Fix Released => New

** Changed in: linux-ti-omap4 (Ubuntu Precise)
       Status: Fix Released => New

** Changed in: linux-ti-omap4 (Ubuntu Saucy)
       Status: Fix Committed => New

** Changed in: linux-ti-omap4 (Ubuntu Quantal)
       Status: Fix Released => New

** Description changed:

- The Linux kernel through 3.7.9 allows local users to obtain sensitive
- information about keystroke timing by using the inotify API on the
- /dev/ptmx device.
+ The timeout pointer parameter is provided by userland (hence the __user
+ annotation) but for x32 syscalls it's simply cast to a kernel pointer
+ and is passed to __sys_recvmmsg which will eventually directly
+ dereference it for both reading and writing. Other callers to
+ __sys_recvmmsg properly copy from userland to the kernel first. The
+ impact is a sort of arbitrary kernel write-where-what primitive by
+ unprivileged users where the to-be-written area must contain valid
+ timespec data initially (the first 64 bit long field must be positive
+ and the second one must be < 1G).
  
- Break-Fix: - b0de59b5733d18b0d1974a060860a8b5c1b36a2e
- Break-Fix: - 37b7f3c76595e23257f61bd80b223de8658617ee
- Break-Fix: - b0b885657b6c8ef63a46bc9299b2a7715d19acde
+ Break-Fix: ee4fa23c4bfcc635d077a9633d405610de45bc70 -

-- 
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/1097680

Title:
  CVE-2013-0160

Status in “linux” package in Ubuntu:
  New
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-natty” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-oneiric” package in Ubuntu:
  Invalid
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  In Progress
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Invalid
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-oneiric” source package in Lucid:
  Invalid
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  New
Status in “linux-armadaxp” source package in Precise:
  New
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Invalid
Status in “linux-lts-backport-natty” source package in Precise:
  Invalid
Status in “linux-lts-backport-oneiric” source package in Precise:
  Invalid
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  Invalid
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  New
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Invalid
Status in “linux-lts-backport-natty” source package in Quantal:
  Invalid
Status in “linux-lts-backport-oneiric” source package in Quantal:
  Invalid
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux-lts-backport-maverick” source package in Raring:
  Invalid
Status in “linux-lts-backport-natty” source package in Raring:
  Invalid
Status in “linux-lts-backport-oneiric” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  New
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Invalid
Status in “linux-lts-backport-natty” source package in Saucy:
  Invalid
Status in “linux-lts-backport-oneiric” source package in Saucy:
  Invalid
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  New
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Invalid
Status in “linux-lts-backport-natty” source package in Trusty:
  Invalid
Status in “linux-lts-backport-oneiric” source package in Trusty:
  Invalid
Status in “linux-lts-quantal” source package in Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in “linux-mvl-dove” source package in Trusty:
  Invalid
Status in “linux-ti-omap4” source package in Trusty:
  Invalid

Bug description:
  The timeout pointer parameter is provided by userland (hence the
  __user annotation) but for x32 syscalls it's simply cast to a kernel
  pointer and is passed to __sys_recvmmsg which will eventually directly
  dereference it for both reading and writing. Other callers to
  __sys_recvmmsg properly copy from userland to the kernel first. The
  impact is a sort of arbitrary kernel write-where-what primitive by
  unprivileged users where the to-be-written area must contain valid
  timespec data initially (the first 64 bit long field must be positive
  and the second one must be < 1G).

  Break-Fix: ee4fa23c4bfcc635d077a9633d405610de45bc70 -

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