← Back to team overview

kernel-packages team mailing list archive

[Bug 769182] Re: CVE-2010-4249

 

** Tags added: kernel-cve-tracking-bug

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

Title:
  CVE-2010-4249

Status in linux package in Ubuntu:
  Incomplete
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:
  Invalid
Status in linux source package in Lucid:
  Incomplete
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:
  Fix Released
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Maverick:
  Invalid
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:
  Fix Released
Status in linux-ti-omap4 source package in Maverick:
  Fix Released
Status in linux source package in Natty:
  Invalid
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:
  Invalid
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:
  Won't Fix
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:
  CVE-2010-4249

  Vegard Nossum found a unix socket OOM was possible, posting an exploit
  program.

  My analysis is we can eat all LOWMEM memory before unix_gc() being
  called from unix_release_sock(). Moreover, the thread blocked in
  unix_gc() can consume huge amount of time to perform cleanup because of
  huge working set.

  One way to handle this is to have a sensible limit on unix_tot_inflight,
  tested from wait_for_unix_gc() and to force a call to unix_gc() if this
  limit is hit.

  This solves the OOM and also reduce overall latencies, and should not
  slowdown normal workloads.

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