← Back to team overview

kernel-packages team mailing list archive

[Bug 1220199] Re: CVE-2013-2894

 

** Changed in: linux-armadaxp (Ubuntu Precise)
       Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Quantal)
       Status: New => Invalid

** Changed in: linux-ec2 (Ubuntu Lucid)
       Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Precise)
       Status: New => Invalid

** Changed in: linux (Ubuntu Precise)
       Status: New => Invalid

** Changed in: linux (Ubuntu Lucid)
       Status: New => Invalid

** Changed in: linux (Ubuntu Saucy)
       Status: New => Invalid

** Changed in: linux (Ubuntu Quantal)
       Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Precise)
       Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Saucy)
       Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Quantal)
       Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Raring)
       Status: New => Invalid

** Description changed:

  drivers/hid/hid-lenovo-tpkbd.c in the Human Interface Device (HID)
  subsystem in the Linux kernel through 3.11, when CONFIG_HID_LENOVO_TPKBD
  is enabled, allows physically proximate attackers to cause a denial of
  service (heap-based out-of-bounds write) via a crafted device.
  
- Break-Fix: - 0a9cd0a80ac559357c6a90d26c55270ed752aa26
+ Break-Fix: c1dcad2d32d0252e8a3023d20311b52a187ecda3
+ 0a9cd0a80ac559357c6a90d26c55270ed752aa26

-- 
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/1220199

Title:
  CVE-2013-2894

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-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-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
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-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Invalid
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:
  New
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Invalid
Status in “linux” source package in Quantal:
  Invalid
Status in “linux-armadaxp” source package in Quantal:
  Invalid
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Invalid
Status in “linux” source package in Raring:
  New
Status in “linux-armadaxp” source package in Raring:
  Invalid
Status in “linux-ec2” source package in Raring:
  Invalid
Status in “linux-fsl-imx51” source package in Raring:
  Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
Status in “linux-lts-quantal” source package in Raring:
  Invalid
Status in “linux-lts-raring” source package in Raring:
  Invalid
Status in “linux-mvl-dove” source package in Raring:
  Invalid
Status in “linux-ti-omap4” source package in Raring:
  Invalid
Status in “linux” source package in Saucy:
  Invalid
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  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-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Invalid

Bug description:
  drivers/hid/hid-lenovo-tpkbd.c in the Human Interface Device (HID)
  subsystem in the Linux kernel through 3.11, when
  CONFIG_HID_LENOVO_TPKBD is enabled, allows physically proximate
  attackers to cause a denial of service (heap-based out-of-bounds
  write) via a crafted device.

  Break-Fix: c1dcad2d32d0252e8a3023d20311b52a187ecda3
  0a9cd0a80ac559357c6a90d26c55270ed752aa26

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


References