[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux-snapdragon (Ubuntu Xenial) Status: New => Fix Committed -- 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/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New 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-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: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish 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: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish 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-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: Invalid Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New 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: Invalid 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: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-goldfish source package in Xenial: New 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: Invalid 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:
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Tags added: kernel-cve-tracking-bug -- 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/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New 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-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: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish 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: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish 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-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: Invalid Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New 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: Invalid 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: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-goldfish source package in Xenial: New 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: Invalid 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
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux-snapdragon (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-snapdragon (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-snapdragon (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-snapdragon (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-snapdragon (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-snapdragon (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux-snapdragon (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-snapdragon (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New 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-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: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish 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: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish 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-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: Invalid Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New 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: Invalid 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: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: Fix Released ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- 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/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New 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-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: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish 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: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish 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-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: Invalid Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta 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 source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New 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: Invalid Status in linux-lts-trusty source
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux-manta (Ubuntu Xenial) Status: New => Invalid -- 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/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New 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-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: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish 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: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish 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-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: Invalid Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta 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 source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New 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: Invalid 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: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-goldfish source package in Xenial: New 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: Invalid 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: New Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: Invalid Bug
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux-raspi2 (Ubuntu Wily) 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/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New 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-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: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish 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: Invalid 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-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish 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-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: Invalid Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta 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 source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New 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: Invalid 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: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-goldfish source package in Xenial: New 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: Invalid 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: New Status in linux-manta source package in Xenial: New Status in linux-raspi2 source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: Invalid Bug description:
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
This bug was fixed in the package linux-lts-xenial - 4.4.0-13.29~14.04.1
---
linux-lts-xenial (4.4.0-13.29~14.04.1) trusty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1556247
* s390/mm: four page table levels vs. fork (LP: #1556141)
- s390/mm: four page table levels vs. fork
* [Hyper-V] network performance patches for Xenial 16.04 (LP: #1556037)
- hv_netvsc: use skb_get_hash() instead of a homegrown implementation
- hv_netvsc: cleanup netdev feature flags for netvsc
* fails to boot on megaraid (LP: #1552903)
- SAUCE: (noup) megaraid_sas: Don't issue kill adapter for MFI controllers
in
case of PD list DCMD failure
* ALSA: hda - add codec support for Kabylake display audio codec (LP:
#1556002)
- ALSA: hda - add codec support for Kabylake display audio codec
* Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Free 'chips' on module exit
- cpufreq: powernv: Hot-plug safe the kworker thread
- cpufreq: powernv: Remove cpu_to_chip_id() from hot-path
- cpufreq: powernv/tracing: Add powernv_throttle tracepoint
- cpufreq: powernv: Replace pr_info with trace print for throttle event
- SAUCE: (noup) cpufreq: powernv: Fix bugs in powernv_cpufreq_{init/exit}
* Linux netfilter IPT_SO_SET_REPLACE memory corruption (LP: #1555338)
- SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving userspace
* integer overflow in xt_alloc_table_info (LP: #1555353)
- SAUCE: (noup) netfilter: x_tables: check for size overflow
* linux: auto-generate the reconstruct information from the git tag (LP:
#143)
- [Packaging] reconstruct -- automatically reconstruct against base tag
- [Config] reconstruct -- update to autoreconstruct output
- [Packaging] reconstruct -- update when inserting final changes
* Xenial update to v4.4.5 stable release (LP: #1555640)
- use ->d_seq to get coherency between ->d_inode and ->d_flags
- drivers: sh: Restore legacy clock domain on SuperH platforms
- Btrfs: fix deadlock running delayed iputs at transaction commit time
- btrfs: Fix no_space in write and rm loop
- btrfs: async-thread: Fix a use-after-free error for trace
- block: Initialize max_dev_sectors to 0
- PCI: keystone: Fix MSI code that retrieves struct pcie_port pointer
- parisc: Fix ptrace syscall number and return value modification
- mips/kvm: fix ioctl error handling
- kvm: x86: Update tsc multiplier on change.
- fbcon: set a default value to blink interval
- cifs: fix out-of-bounds access in lease parsing
- CIFS: Fix SMB2+ interim response processing for read requests
- Fix cifs_uniqueid_to_ino_t() function for s390x
- vfio: fix ioctl error handling
- KVM: x86: fix root cause for missed hardware breakpoints
- arm/arm64: KVM: Fix ioctl error handling
- iommu/amd: Apply workaround for ATS write permission check
- iommu/amd: Fix boot warning when device 00:00.0 is not iommu covered
- iommu/vt-d: Use BUS_NOTIFY_REMOVED_DEVICE in hotplug path
- target: Fix WRITE_SAME/DISCARD conversion to linux 512b sectors
- drm/ast: Fix incorrect register check for DRAM width
- drm/radeon/pm: update current crtc info after setting the powerstate
- drm/amdgpu/pm: update current crtc info after setting the powerstate
- drm/amdgpu: apply gfx_v8 fixes to gfx_v7 as well
- drm/amdgpu/gfx8: specify which engine to wait before vm flush
- drm/amdgpu: return from atombios_dp_get_dpcd only when error
- libata: fix HDIO_GET_32BIT ioctl
- libata: Align ata_device's id on a cacheline
- block: bio: introduce helpers to get the 1st and last bvec
- writeback: flush inode cgroup wb switches instead of pinning super_block
- Adding Intel Lewisburg device IDs for SATA
- arm64: vmemmap: use virtual projection of linear region
- PM / sleep / x86: Fix crash on graph trace through x86 suspend
- ata: ahci: don't mark HotPlugCapable Ports as external/removable
- tracing: Do not have 'comm' filter override event 'comm' field
- pata-rb532-cf: get rid of the irq_to_gpio() call
- Btrfs: fix loading of orphan roots leading to BUG_ON
- Revert "jffs2: Fix lock acquisition order bug in jffs2_write_begin"
- jffs2: Fix page lock / f->sem deadlock
- Fix directory hardlinks from deleted directories
- dmaengine: pxa_dma: fix cyclic transfers
- adv7604: fix tx 5v detect regression
- ALSA: usb-audio: Add a quirk for Plantronics DA45
- ALSA: ctl: Fix ioctls for X32 ABI
- ALSA: hda - Fix mic issues on Acer Aspire E1-472
- ALSA: rawmidi: Fix ioctls X32 ABI
- ALSA: timer: Fix ioctls for X32 ABI
- ALSA: pcm: Fix ioctls for X32 ABI
- ALSA: seq: oss: Don't drain at closing a client
- ALSA: hdspm: Fix wrong boolean ctl value accesses
- ALSA: hdsp: Fix wrong boolean ctl value accesses
- ALSA: hdspm: Fix zero-division
- ALSA:
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
This bug was fixed in the package linux - 4.4.0-13.29
---
linux (4.4.0-13.29) xenial; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1556247
* s390/mm: four page table levels vs. fork (LP: #1556141)
- s390/mm: four page table levels vs. fork
* [Hyper-V] network performance patches for Xenial 16.04 (LP: #1556037)
- hv_netvsc: use skb_get_hash() instead of a homegrown implementation
- hv_netvsc: cleanup netdev feature flags for netvsc
* fails to boot on megaraid (LP: #1552903)
- SAUCE: (noup) megaraid_sas: Don't issue kill adapter for MFI controllers
in
case of PD list DCMD failure
* ALSA: hda - add codec support for Kabylake display audio codec (LP:
#1556002)
- ALSA: hda - add codec support for Kabylake display audio codec
* Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Free 'chips' on module exit
- cpufreq: powernv: Hot-plug safe the kworker thread
- cpufreq: powernv: Remove cpu_to_chip_id() from hot-path
- cpufreq: powernv/tracing: Add powernv_throttle tracepoint
- cpufreq: powernv: Replace pr_info with trace print for throttle event
- SAUCE: (noup) cpufreq: powernv: Fix bugs in powernv_cpufreq_{init/exit}
* Linux netfilter IPT_SO_SET_REPLACE memory corruption (LP: #1555338)
- SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving userspace
* integer overflow in xt_alloc_table_info (LP: #1555353)
- SAUCE: (noup) netfilter: x_tables: check for size overflow
* linux: auto-generate the reconstruct information from the git tag (LP:
#143)
- [Packaging] reconstruct -- automatically reconstruct against base tag
- [Config] reconstruct -- update to autoreconstruct output
- [Packaging] reconstruct -- update when inserting final changes
* Xenial update to v4.4.5 stable release (LP: #1555640)
- use ->d_seq to get coherency between ->d_inode and ->d_flags
- drivers: sh: Restore legacy clock domain on SuperH platforms
- Btrfs: fix deadlock running delayed iputs at transaction commit time
- btrfs: Fix no_space in write and rm loop
- btrfs: async-thread: Fix a use-after-free error for trace
- block: Initialize max_dev_sectors to 0
- PCI: keystone: Fix MSI code that retrieves struct pcie_port pointer
- parisc: Fix ptrace syscall number and return value modification
- mips/kvm: fix ioctl error handling
- kvm: x86: Update tsc multiplier on change.
- fbcon: set a default value to blink interval
- cifs: fix out-of-bounds access in lease parsing
- CIFS: Fix SMB2+ interim response processing for read requests
- Fix cifs_uniqueid_to_ino_t() function for s390x
- vfio: fix ioctl error handling
- KVM: x86: fix root cause for missed hardware breakpoints
- arm/arm64: KVM: Fix ioctl error handling
- iommu/amd: Apply workaround for ATS write permission check
- iommu/amd: Fix boot warning when device 00:00.0 is not iommu covered
- iommu/vt-d: Use BUS_NOTIFY_REMOVED_DEVICE in hotplug path
- target: Fix WRITE_SAME/DISCARD conversion to linux 512b sectors
- drm/ast: Fix incorrect register check for DRAM width
- drm/radeon/pm: update current crtc info after setting the powerstate
- drm/amdgpu/pm: update current crtc info after setting the powerstate
- drm/amdgpu: apply gfx_v8 fixes to gfx_v7 as well
- drm/amdgpu/gfx8: specify which engine to wait before vm flush
- drm/amdgpu: return from atombios_dp_get_dpcd only when error
- libata: fix HDIO_GET_32BIT ioctl
- libata: Align ata_device's id on a cacheline
- block: bio: introduce helpers to get the 1st and last bvec
- writeback: flush inode cgroup wb switches instead of pinning super_block
- Adding Intel Lewisburg device IDs for SATA
- arm64: vmemmap: use virtual projection of linear region
- PM / sleep / x86: Fix crash on graph trace through x86 suspend
- ata: ahci: don't mark HotPlugCapable Ports as external/removable
- tracing: Do not have 'comm' filter override event 'comm' field
- pata-rb532-cf: get rid of the irq_to_gpio() call
- Btrfs: fix loading of orphan roots leading to BUG_ON
- Revert "jffs2: Fix lock acquisition order bug in jffs2_write_begin"
- jffs2: Fix page lock / f->sem deadlock
- Fix directory hardlinks from deleted directories
- dmaengine: pxa_dma: fix cyclic transfers
- adv7604: fix tx 5v detect regression
- ALSA: usb-audio: Add a quirk for Plantronics DA45
- ALSA: ctl: Fix ioctls for X32 ABI
- ALSA: hda - Fix mic issues on Acer Aspire E1-472
- ALSA: rawmidi: Fix ioctls X32 ABI
- ALSA: timer: Fix ioctls for X32 ABI
- ALSA: pcm: Fix ioctls for X32 ABI
- ALSA: seq: oss: Don't drain at closing a client
- ALSA: hdspm: Fix wrong boolean ctl value accesses
- ALSA: hdsp: Fix wrong boolean ctl value accesses
- ALSA: hdspm: Fix zero-division
- ALSA: timer: Fix broken compat timer user status
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-quantal (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-raring (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-xenial (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-saucy (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-manta (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-manta (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-raspi2 (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-raspi2 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-mako (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-mako (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-utopic (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-utopic (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-goldfish (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-goldfish (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-flo (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-flo (Ubuntu Xenial) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-quantal (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-raring (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mako (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-manta (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-goldfish (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-flo (Ubuntu Trusty)
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
This bug was fixed in the package linux - 4.2.0-34.39 --- linux (4.2.0-34.39) wily; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1555821 [ Florian Westphal ] * SAUCE: [nf] netfilter: x_tables: check for size overflow - LP: #1555353 * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving userspace - LP: #1555338 linux (4.2.0-33.38) wily; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1554649 [ Upstream Kernel Changes ] * Revert "drm/radeon: call hpd_irq_event on resume" - LP: #1554608 * cxl: Fix PSL timebase synchronization detection - LP: #1532914 linux (4.2.0-32.37) wily; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1550045 [ Kamal Mostafa ] * Merged back Ubuntu-4.2.0-31.36 linux (4.2.0-31.36) wily; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1548579 [ Andy Whitcroft ] * [Debian] hv: hv_set_ifconfig -- convert to python3 - LP: #1506521 * [Debian] hv: hv_set_ifconfig -- switch to approved indentation - LP: #1540586 * [Debian] hv: hv_set_ifconfig -- fix numerous parameter handling issues - LP: #1540586 [ Carol L Soto ] * SAUCE: IB/IPoIB: Do not set skb truesize since using one linearskb - LP: #1541326 [ Dan Streetman ] * SAUCE: nbd: ratelimit error msgs after socket close - LP: #1505564 [ Tim Gardner ] * Revert "SAUCE: (noup) cxlflash: Fix to avoid virtual LUN failover failure" - LP: #1541635 * Revert "SAUCE: (noup) cxlflash: Fix to escalate LINK_RESET also on port 1" - LP: #1541635 * [Config] ARMV8_DEPRECATED=y - LP: #1545542 [ Upstream Kernel Changes ] * x86/xen/p2m: hint at the last populated P2M entry - LP: #1542941 * mm: add dma_pool_zalloc() call to DMA API - LP: #1543737 * sctp: Prevent soft lockup when sctp_accept() is called during a timeout event - LP: #1543737 * xen-netback: respect user provided max_queues - LP: #1543737 * xen-netfront: respect user provided max_queues - LP: #1543737 * xen-netfront: update num_queues to real created - LP: #1543737 * iio: adis_buffer: Fix out-of-bounds memory access - LP: #1543737 * KVM: PPC: Fix emulation of H_SET_DABR/X on POWER8 - LP: #1543737 * KVM: PPC: Fix ONE_REG AltiVec support - LP: #1543737 * x86/irq: Call chip->irq_set_affinity in proper context - LP: #1543737 * drm/amdgpu: fix tonga smu resume - LP: #1543737 * perf kvm record/report: 'unprocessable sample' error while recording/reporting guest data - LP: #1543737 * hrtimer: Handle remaining time proper for TIME_LOW_RES - LP: #1543737 * timerfd: Handle relative timers with CONFIG_TIME_LOW_RES proper - LP: #1543737 * posix-timers: Handle relative timers with CONFIG_TIME_LOW_RES proper - LP: #1543737 * itimers: Handle relative timers with CONFIG_TIME_LOW_RES proper - LP: #1543737 * drm/amdgpu: Use drm_calloc_large for VM page_tables array - LP: #1543737 * drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2 - LP: #1543737 * drm/radeon: properly byte swap vce firmware setup - LP: #1543737 * ACPI: Revert "ACPI / video: Add Dell Inspiron 5737 to the blacklist" - LP: #1543737 * ACPI / PCI / hotplug: unlock in error path in acpiphp_enable_slot() - LP: #1543737 * hwmon: (dell-smm) Blacklist Dell Studio XPS 8000 - LP: #1543737 * usb: cdc-acm: handle unlinked urb in acm read callback - LP: #1543737 * usb: cdc-acm: send zero packet for intel 7260 modem - LP: #1543737 * cdc-acm:exclude Samsung phone 04e8:685d - LP: #1543737 * usb: hub: do not clear BOS field during reset device - LP: #1543737 * USB: cp210x: add ID for IAI USB to RS485 adaptor - LP: #1543737 * USB: visor: fix null-deref at probe - LP: #1543737 * USB: serial: visor: fix crash on detecting device without write_urbs - LP: #1543737 * USB: serial: option: Adding support for Telit LE922 - LP: #1543737 * ALSA: seq: Fix incorrect sanity check at snd_seq_oss_synth_cleanup() - LP: #1543737 * ALSA: seq: Degrade the error message for too many opens - LP: #1543737 * USB: serial: ftdi_sio: add support for Yaesu SCU-18 cable - LP: #1543737 * arm64: kernel: fix architected PMU registers unconditional access - LP: #1543737 * USB: option: fix Cinterion AHxx enumeration - LP: #1543737 * ALSA: compress: Disable GET_CODEC_CAPS ioctl for some architectures - LP: #1543737 * ALSA: usb-audio: Fix TEAC UD-501/UD-503/NT-503 usb delay - LP: #1543737 * virtio_pci: fix use after free on release - LP: #1543737 * ALSA: bebob: Use a signed return type for get_formation_index - LP: #1543737 * arm64: errata: Add -mpc-relative-literal-loads to build flags - LP: #1533009, #1543737 * arm64: mm: avoid calling apply_to_page_range on empty range - LP: #1543737 * x86/mm: Fix types used in pgprot
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
This has been assigned CVE-2016-3135 ( http://www.openwall.com/lists /oss-security/2016/03/14/1 ). ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-3135 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Tags added: kernel-cve-skip-description -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: [Impact] [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Description changed: + [Impact] + [From https://code.google.com/p/google-security- research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: - + size_t sz = sizeof(*info) + size; + + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). + + [Fix] + Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 + + [Test Case] + Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 + gcc *v4.c -o v4 + ./v4 + Your machine should _not_ crash. This only affects 32-bit kernels ** Description changed: [Impact] - - [From https://code.google.com/p/google-security- - research/issues/detail?id=758 ] + [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Committed Bug description: [Impact] [From https://code.google.com/p/google-security-research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). [Fix] Upstream proposed fix: http://marc.info/?l=netfilter-devel=145757136822750=2 [Test Case] Download v4 code from: https://code.google.com/p/google-security-research/issues/detail?id=758 gcc *v4.c -o v4 ./v4 Your machine should _not_ crash. This only affects 32-bit kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Committed Bug description: [From https://code.google.com/p/google-security- research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Chris J Arges (arges) ** Changed in: linux (Ubuntu Wily) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: [From https://code.google.com/p/google-security- research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: New Status in linux source package in Xenial: In Progress Bug description: [From https://code.google.com/p/google-security- research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info
Upstream proposed fix: http://marc.info/?l=netfilter- devel=145757136822750=2 ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555353 Title: integer overflow in xt_alloc_table_info Status in linux package in Ubuntu: Confirmed Bug description: [From https://code.google.com/p/google-security- research/issues/detail?id=758 ] A recent refactoring cof this codepath (https://github.com/torvalds/linux/commit/2e4e6a17af35be359cc8f1c924f8f198fbd478cc) introduced an integer overflow in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. More specifically, the overflow may have been introduced in https://github.com/torvalds/linux/commit/711bdde6a884354ddae8da2fcb495b2a9364cc90 ; specifically the bit: + size_t sz = sizeof(*info) + size; (where size is an unsigned int passed from userspace). This issue should only affect 32bit platforms (xt_table_info.size is an unsigned int). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
