kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #93959
[Bug 963685] Re: Please consider backporting killable request_module() patchset
** Changed in: linux-lts-trusty (Ubuntu Vivid)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Vivid)
Importance: Undecided => Medium
** Changed in: linux-lts-utopic (Ubuntu Vivid)
Status: New => Invalid
** Changed in: linux-lts-utopic (Ubuntu Vivid)
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/963685
Title:
Please consider backporting killable request_module() patchset
Status in linux package in Ubuntu:
Fix Released
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-lts-trusty package in Ubuntu:
Invalid
Status in linux-lts-utopic 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:
Fix Released
Status in linux-armadaxp source package in Lucid:
Invalid
Status in linux-ec2 source package in Lucid:
Fix Released
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:
Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
Fix Released
Status in linux-lts-quantal source package in Lucid:
Invalid
Status in linux-lts-raring 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-lts-backport-maverick source package in Oneiric:
Invalid
Status in linux-lts-backport-natty source package in Oneiric:
Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
Invalid
Status in linux source package in Precise:
Fix Released
Status in linux-armadaxp source package in Precise:
Invalid
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:
Invalid
Status in linux-lts-raring source package in Precise:
Invalid
Status in linux-mvl-dove 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:
Fix Released
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-mvl-dove source package in Trusty:
Invalid
Status in linux-ti-omap4 source package in Trusty:
Invalid
Status in linux source package in Utopic:
Fix Released
Status in linux-armadaxp source package in Utopic:
Invalid
Status in linux-ec2 source package in Utopic:
Invalid
Status in linux-fsl-imx51 source package in Utopic:
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-lts-quantal source package in Utopic:
Invalid
Status in linux-lts-raring source package in Utopic:
Invalid
Status in linux-mvl-dove source package in Utopic:
Invalid
Status in linux-ti-omap4 source package in Utopic:
Invalid
Status in linux source package in Vivid:
Fix Released
Status in linux-armadaxp source package in Vivid:
Invalid
Status in linux-ec2 source package in Vivid:
Invalid
Status in linux-fsl-imx51 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:
Invalid
Status in linux-lts-trusty source package in Vivid:
Invalid
Status in linux-lts-utopic source package in Vivid:
Invalid
Status in linux-mvl-dove source package in Vivid:
Invalid
Status in linux-ti-omap4 source package in Vivid:
Invalid
Status in linux-lts-backport-maverick source package in Hardy:
Invalid
Status in linux-lts-backport-natty source package in Hardy:
Invalid
Status in linux-lts-backport-oneiric source package in Hardy:
Invalid
Bug description:
The __request_module function in kernel/kmod.c in the Linux kernel
before 3.4 does not set a certain killable attribute, which allows
local users to cause a denial of service (memory consumption) via a
crafted application.
Break-Fix: - 70834d3070c3f3015ab5c05176d54bd4a0100546
Break-Fix: - b3449922502f5a161ee2b5022a33aec8472fbf18
Break-Fix: - d0bd587a80960d7ba7e0c8396e154028c9045c54
Break-Fix: - 9d944ef32e83405a07376f112e9f02161d3e9731
Break-Fix: - 5b9bd473e3b8a8c6c4ae99be475e6e9b27568555
Break-Fix: - 3e63a93b987685f02421e18b2aa452d20553a88b
Break-Fix: - 1cc684ab75123efe7ff446eb821d44375ba8fa30
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685/+subscriptions