kernel-packages team mailing list archive

[John Johansen <john.johansen@xxxxxxxxxxxxx>]

** Also affects: linux (Ubuntu Utopic)
   Importance: Medium
       Status: New

** Also affects: linux-fsl-imx51 (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-ec2 (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Utopic)
   Importance: Undecided
       Status: Won't Fix

** Also affects: linux-lts-backport-natty (Ubuntu Utopic)
   Importance: Undecided
       Status: Won't Fix

** Also affects: linux-armadaxp (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Utopic)
   Importance: Medium
       Status: Invalid

** Changed in: linux-lts-raring (Ubuntu Precise)
       Status: Won't Fix => New

** Description changed:

- Linux kernel built with the InfiniBand communication
- link(CONFIG_INFINIBAND) along with the support for Remote Direct Memory
- Access(RDMA) over Convered Ethernet(RoCE), is vulnerable to a crash
- caused by invalid memory access. It occurs while trying to resolve RoCE
- L2 address on the server side. A remote unprivileged user/program could
- use this flaw to crash the kernel, resulting in DoS.
+ The cma_req_handler function in drivers/infiniband/core/cma.c in the
+ Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over
+ Converged Ethernet (aka RoCE) address that is properly resolved within a
+ different module, which allows remote attackers to cause a denial of
+ service (incorrect pointer dereference and system crash) via crafted
+ network traffic.
  
  Break-Fix: dd5f03beb4f76ae65d76d8c22a8815e424fc607c
  b2853fd6c2d0f383dbdf7427e263eb576a633867

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

Title:
  CVE-2014-2739

Status in “linux” package in Ubuntu:
  New
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:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
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:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
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:
  New
Status in “linux-armadaxp” source package in Precise:
  New
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:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  New
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  New
Status in “linux” source package in Quantal:
  New
Status in “linux-armadaxp” source package in Quantal:
  New
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:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  New
Status in “linux” source package in Saucy:
  New
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:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  New
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:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
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:
  New
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:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Utopic:
  Won't Fix
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:
  The cma_req_handler function in drivers/infiniband/core/cma.c in the
  Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over
  Converged Ethernet (aka RoCE) address that is properly resolved within
  a different module, which allows remote attackers to cause a denial of
  service (incorrect pointer dereference and system crash) via crafted
  network traffic.

  Break-Fix: dd5f03beb4f76ae65d76d8c22a8815e424fc607c
  b2853fd6c2d0f383dbdf7427e263eb576a633867

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