kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #162623
[Bug 1549200] Re: CVE-2016-2549
CVE-2016-2549
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-ti-omap4 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: linux-ti-omap4 (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux-ti-omap4 (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-ti-omap4 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux-ti-omap4 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux-lts-trusty (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-quantal (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-quantal (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-quantal (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-ti-omap4 (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-ti-omap4 (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-ti-omap4 (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-raring (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-raring (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-raring (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-armadaxp (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-armadaxp (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-armadaxp (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-xenial (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-xenial (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-xenial (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-saucy (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-saucy (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-saucy (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-manta (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-vivid (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-vivid (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-vivid (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-raspi2 (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-raspi2 (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-mako (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-utopic (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-utopic (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-utopic (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-goldfish (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-flo (Ubuntu Precise)
Status: New => Invalid
** Description changed:
- Placeholder
+ hrtimer_cancel() waits for the completion from the callback, thus it
+ must not be called inside the callback itself. This was already a
+ problem in the past with ALSA hrtimer driver, and the early commit
+ [fcfdebe70759: ALSA: hrtimer - Fix lock-up] tried to address it.
+ However, the previous fix is still insufficient: it may still cause a
+ lockup when the ALSA timer instance reprograms itself in its callback.
+ Then it invokes the start function even in snd_timer_interrupt() that is
+ called in hrtimer callback itself, results in a CPU stall. This is no
+ hypothetical problem but actually triggered by syzkaller fuzzer.
+
+ Break-Fix: - 2ba1fe7a06d3624f9a7586d672b55f08f7c670f3
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-trusty (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-trusty (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-quantal (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-quantal (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-quantal (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-quantal (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-ti-omap4 (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-ti-omap4 (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-ti-omap4 (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-ti-omap4 (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-raring (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-raring (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-raring (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-raring (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-raring (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-armadaxp (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-armadaxp (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-armadaxp (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-armadaxp (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-xenial (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-xenial (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-xenial (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-xenial (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-saucy (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-saucy (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-saucy (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-manta (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-manta (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-manta (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-manta (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-manta (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-vivid (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-vivid (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-vivid (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-raspi2 (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-raspi2 (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-raspi2 (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-raspi2 (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-mako (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-mako (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-mako (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-mako (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-mako (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-lts-utopic (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-utopic (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-lts-utopic (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-goldfish (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-goldfish (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-goldfish (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-goldfish (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-goldfish (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-flo (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-flo (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux-flo (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-flo (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-flo (Ubuntu Trusty)
Importance: Undecided => Medium
--
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/1549200
Title:
CVE-2016-2549
Status in linux package in Ubuntu:
New
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:
New
Status in linux-armadaxp source package in Precise:
New
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:
New
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:
New
Status in linux source package in Trusty:
New
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:
New
Status in linux-lts-vivid source package in Trusty:
New
Status in linux-lts-wily source package in Trusty:
New
Status in linux-lts-xenial source package in Trusty:
New
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 Vivid:
New
Status in linux-armadaxp source package in Vivid:
New
Status in linux-flo source package in Vivid:
New
Status in linux-goldfish source package in Vivid:
New
Status in linux-lts-quantal source package in Vivid:
New
Status in linux-lts-raring source package in Vivid:
New
Status in linux-lts-saucy source package in Vivid:
New
Status in linux-lts-trusty source package in Vivid:
New
Status in linux-lts-utopic source package in Vivid:
New
Status in linux-lts-vivid source package in Vivid:
New
Status in linux-lts-wily source package in Vivid:
New
Status in linux-lts-xenial source package in Vivid:
New
Status in linux-mako source package in Vivid:
New
Status in linux-manta source package in Vivid:
New
Status in linux-raspi2 source package in Vivid:
New
Status in linux-ti-omap4 source package in Vivid:
New
Status in linux source package in Wily:
New
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:
New
Status in linux-ti-omap4 source package in Wily:
Invalid
Status in linux source package in Xenial:
New
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:
hrtimer_cancel() waits for the completion from the callback, thus it
must not be called inside the callback itself. This was already a
problem in the past with ALSA hrtimer driver, and the early commit
[fcfdebe70759: ALSA: hrtimer - Fix lock-up] tried to address it.
However, the previous fix is still insufficient: it may still cause a
lockup when the ALSA timer instance reprograms itself in its callback.
Then it invokes the start function even in snd_timer_interrupt() that
is called in hrtimer callback itself, results in a CPU stall. This is
no hypothetical problem but actually triggered by syzkaller fuzzer.
Break-Fix: - 2ba1fe7a06d3624f9a7586d672b55f08f7c670f3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549200/+subscriptions
References