kernel-packages team mailing list archive

[Rolf Leggewie <723945@xxxxxxxxxxxxxxxxxx>]

lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".

** Changed in: linux-mvl-dove (Ubuntu Lucid)
       Status: In Progress => Won't Fix

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

Title:
  CVE-2010-4258

Status in linux package in Ubuntu:
  Fix Released
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Fix Released
Status in linux-fsl-imx51 source package in Lucid:
  Fix Released
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-mvl-dove source package in Lucid:
  Won't Fix
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Maverick:
  Fix Released
Status in linux-fsl-imx51 source package in Maverick:
  Invalid
Status in linux-lts-backport-maverick source package in Maverick:
  Won't Fix
Status in linux-mvl-dove source package in Maverick:
  Won't Fix
Status in linux-ti-omap4 source package in Maverick:
  Fix Released
Status in linux source package in Natty:
  Fix Released
Status in linux-fsl-imx51 source package in Natty:
  Invalid
Status in linux-lts-backport-maverick source package in Natty:
  Invalid
Status in linux-mvl-dove source package in Natty:
  Invalid
Status in linux-ti-omap4 source package in Natty:
  Fix Released
Status in linux source package in Dapper:
  Won't Fix
Status in linux-fsl-imx51 source package in Dapper:
  Invalid
Status in linux-lts-backport-maverick source package in Dapper:
  Won't Fix
Status in linux-mvl-dove source package in Dapper:
  Invalid
Status in linux-ti-omap4 source package in Dapper:
  Invalid
Status in linux source package in Hardy:
  Fix Released
Status in linux-fsl-imx51 source package in Hardy:
  Invalid
Status in linux-lts-backport-maverick source package in Hardy:
  Won't Fix
Status in linux-mvl-dove source package in Hardy:
  Invalid
Status in linux-ti-omap4 source package in Hardy:
  Invalid
Status in linux source package in Karmic:
  Fix Released
Status in linux-fsl-imx51 source package in Karmic:
  Won't Fix
Status in linux-lts-backport-maverick source package in Karmic:
  Won't Fix
Status in linux-mvl-dove source package in Karmic:
  Invalid
Status in linux-ti-omap4 source package in Karmic:
  Invalid

Bug description:
  If a user manages to trigger an oops with fs set to KERNEL_DS, fs is not
  otherwise reset before do_exit().  do_exit may later (via mm_release in
  fork.c) do a put_user to a user-controlled address, potentially allowing
  a user to leverage an oops into a controlled write into kernel memory.

  This is only triggerable in the presence of another bug, but this
  potentially turns a lot of DoS bugs into privilege escalations, so it's
  worth fixing.  I have proof-of-concept code which uses this bug along
  with CVE-2010-3849 to write a zero to an arbitrary kernel address, so
  I've tested that this is not theoretical.

  A more logical place to put this fix might be when we know an oops has
  occurred, before we call do_exit(), but that would involve changing
  every architecture, in multiple places.

  Let's just stick it in do_exit instead.

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