kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #77696
[Bug 1334989] Re: CVE-2014-4508
This bug was fixed in the package linux-ec2 - 2.6.32-369.85
---------------
linux-ec2 (2.6.32-369.85) lucid; urgency=low
[ Stefan Bader ]
* Rebased to Ubuntu-2.6.32-65.129
* Rebased to Ubuntu-2.6.32-65.131
* Release Tracking Bug
- LP: #1357410
[ Upstream Kernel Changes ]
* xen: x86_32, entry: Do syscall exit work on badsys (CVE-2014-4508)
- LP: #1334989
- CVE-2014-4508
* xen: x86_32, entry: Store badsys error code in %eax
- LP: #1334989
- CVE-2014-4508
[ Ubuntu: 2.6.32-65.131 ]
* x86_32, entry: Store badsys error code in %eax
- LP: #1334989
- CVE-2014-4508
[ Ubuntu: 2.6.32-65.129 ]
* fix autofs/afs/etc. magic mountpoint breakage
- CVE-2014-0203
* ALSA: control: Don't access controls outside of protected regions
- LP: #1339297
- CVE-2014-4653
* ALSA: control: Fix replacing user controls
- LP: #1339303, #1339304
- CVE-2014-4655
* ALSA: control: Handle numid overflow
- LP: #1339306
- CVE-2014-4656
* ALSA: control: Make sure that id->index does not overflow
- LP: #1339306
- CVE-2014-4656
* sctp: Fix sk_ack_backlog wrap-around problem
- CVE-2014-4667
* x86_32, entry: Do syscall exit work on badsys (CVE-2014-4508)
- LP: #1334989
- CVE-2014-4508
* ALSA: control: Protect user controls against concurrent access
- LP: #1339294
- CVE-2014-4652
* net: sctp: inherit auth_capable on INIT collisions
- LP: #1349804
- CVE-2014-5077
-- Stefan Bader <stefan.bader@xxxxxxxxxxxxx> Fri, 15 Aug 2014 08:55:05 +0200
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: Fix Committed => 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/1334989
Title:
CVE-2014-4508
Status in “linux” package in Ubuntu:
Fix Committed
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:
New
Status in “linux-lts-backport-natty” 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-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:
New
Status in “linux-lts-backport-natty” source package in Lucid:
New
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status in “linux-lts-saucy” 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” source package in Precise:
Fix Committed
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:
New
Status in “linux-lts-backport-natty” source package in Precise:
New
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-mvl-dove” source package in Precise:
Invalid
Status in “linux-ti-omap4” source package in Precise:
Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
New
Status in “linux-lts-backport-natty” source package in Saucy:
New
Status in “linux” source package in Trusty:
Fix Committed
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:
New
Status in “linux-lts-backport-natty” source package in Trusty:
New
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-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 Committed
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:
New
Status in “linux-lts-backport-natty” source package in Utopic:
New
Status in “linux-lts-quantal” source package in Utopic:
Invalid
Status in “linux-lts-raring” source package in Utopic:
Invalid
Status in “linux-lts-saucy” 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
Bug description:
arch/x86/kernel/entry_32.S in the Linux kernel through 3.15.1 on
32-bit x86 platforms, when syscall auditing is enabled and the sep CPU
feature flag is set, allows local users to cause a denial of service
(OOPS and system crash) via an invalid syscall number, as demonstrated
by number 1000.
Break-Fix: - 554086d85e71f30abe46fc014fea31929a7c6a8a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334989/+subscriptions
References