group.of.nepali.translators team mailing list archive

Thread
Date
[Bug 947997] Closing unsupported series nomination.

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Andy Whitcroft <apw@xxxxxxxxxxxxx>
Date: Tue, 17 Oct 2017 16:25:31 -0000
Reply-to: Bug 947997 <947997@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
This bug was nominated against a series that is no longer supported, ie
vivid.  The bug task representing the vivid nomination is being closed
as Won't Fix.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux-lts-saucy (Ubuntu Vivid)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/947997

Title:
  CVE-2012-1090

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish 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:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
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-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-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 source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish 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:
  New
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Invalid
Status in linux-lts-backport-natty source package in Utopic:
  Invalid
Status in linux-lts-backport-oneiric source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  Invalid
Status in linux-lts-backport-natty source package in Vivid:
  Invalid
Status in linux-lts-backport-oneiric source package in Vivid:
  Invalid
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Won't Fix
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-lts-wily source package in Vivid:
  Invalid
Status in linux-lts-xenial source package in Vivid:
  Won't Fix
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-raspi2 source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  Invalid
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  Invalid
Status in linux-lts-backport-maverick source package in Wily:
  Invalid
Status in linux-lts-backport-natty source package in Wily:
  Invalid
Status in linux-lts-backport-oneiric source package in Wily:
  Invalid
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  New
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  Invalid
Status in linux-manta source package in Wily:
  Invalid
Status in linux-mvl-dove source package in Wily:
  Invalid
Status in linux-raspi2 source package in Wily:
  Invalid
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-ec2 source package in Xenial:
  Invalid
Status in linux-flo source package in Xenial:
  Invalid
Status in linux-fsl-imx51 source package in Xenial:
  Invalid
Status in linux-goldfish source package in Xenial:
  Invalid
Status in linux-lts-backport-maverick source package in Xenial:
  Invalid
Status in linux-lts-backport-natty source package in Xenial:
  Invalid
Status in linux-lts-backport-oneiric source package in Xenial:
  Invalid
Status in linux-lts-quantal source package in Xenial:
  Invalid
Status in linux-lts-raring source package in Xenial:
  Invalid
Status in linux-lts-saucy source package in Xenial:
  New
Status in linux-lts-trusty source package in Xenial:
  Invalid
Status in linux-lts-utopic source package in Xenial:
  Invalid
Status in linux-lts-vivid source package in Xenial:
  Invalid
Status in linux-lts-wily source package in Xenial:
  Invalid
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux-mako source package in Xenial:
  Invalid
Status in linux-manta source package in Xenial:
  Invalid
Status in linux-mvl-dove source package in Xenial:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Fix Committed
Status in linux-ti-omap4 source package in Xenial:
  Invalid

Bug description:
  The cifs_lookup function in fs/cifs/dir.c in the Linux kernel before
  3.2.10 allows local users to cause a denial of service (OOPS) via
  attempted access to a special file, as demonstrated by a FIFO. "The
  cifs code will attempt to open files on lookup under certain
  circumstances. What happens though if we find that the file we opened
  was actually a FIFO or other special file? Currently, the open
  filehandle just ends up being leaked leading to a dentry refcount
  mismatch and oops on umount."

  Break-Fix: 8db14ca12569fe885694bd3d5ff84c2d973d3cb0
  5bccda0ebc7c0331b81ac47d39e4b920b198b2cd

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