IB/cm: Bump reference count on cm_id before invoking callback, CVE-2011-0695
On 04/25/2011 01:29 PM, Brad Figg wrote:
From: Sean Hefty<sean.hefty@intel.com>
CVE-2011-0695
BugLink: http://bugs.launchpad.net/bugs/770369
When processing a SIDR REQ, the ib_cm allocates a new cm_id. The
refcount of the cm_id is initialized to 1. However, cm_process_work
will decrement the refcount after invoking all callbacks. The result
is that the cm_id will end up with refcount set to 0 by the end of the
sidr req handler.
If a user tries to destroy the cm_id, the destruction will proceed,
under the incorrect assumption that no other threads are referencing
the cm_id. This can lead to a crash when the cm callback thread tries
to access the cm_id.
This problem was noticed as part of a larger investigation with kernel
crashes in the rdma_cm when running on a real time OS.
Signed-off-by: Sean Hefty<sean.hefty@intel.com>
Acked-by: Doug Ledford<dledford@redhat.com>
Cc:<stable@kernel.org>
Signed-off-by: Roland Dreier<roland@purestorage.com>
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
04-25-2011, 08:53 PM
John Johansen
IB/cm: Bump reference count on cm_id before invoking callback, CVE-2011-0695
On 04/25/2011 12:29 PM, Brad Figg wrote:
> From: Sean Hefty <sean.hefty@intel.com>
>
> CVE-2011-0695
>
> BugLink: http://bugs.launchpad.net/bugs/770369
>
> When processing a SIDR REQ, the ib_cm allocates a new cm_id. The
> refcount of the cm_id is initialized to 1. However, cm_process_work
> will decrement the refcount after invoking all callbacks. The result
> is that the cm_id will end up with refcount set to 0 by the end of the
> sidr req handler.
>
> If a user tries to destroy the cm_id, the destruction will proceed,
> under the incorrect assumption that no other threads are referencing
> the cm_id. This can lead to a crash when the cm callback thread tries
> to access the cm_id.
>
> This problem was noticed as part of a larger investigation with kernel
> crashes in the rdma_cm when running on a real time OS.
>
> Signed-off-by: Sean Hefty <sean.hefty@intel.com>
> Acked-by: Doug Ledford <dledford@redhat.com>
> Cc: <stable@kernel.org>
> Signed-off-by: Roland Dreier <roland@purestorage.com>
>
> (cherry-picked from commit 29963437a48475036353b95ab142bf199adb909e)
> Signed-off-by: Brad Figg <brad.figg@canonical.com>
Acked-by: John Johansen <john.johansen@canonical.com>
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
04-26-2011, 12:53 AM
Tim Gardner
IB/cm: Bump reference count on cm_id before invoking callback, CVE-2011-0695
On 04/25/2011 01:29 PM, Brad Figg wrote:
From: Sean Hefty<sean.hefty@intel.com>
CVE-2011-0695
BugLink: http://bugs.launchpad.net/bugs/770369
When processing a SIDR REQ, the ib_cm allocates a new cm_id. The
refcount of the cm_id is initialized to 1. However, cm_process_work
will decrement the refcount after invoking all callbacks. The result
is that the cm_id will end up with refcount set to 0 by the end of the
sidr req handler.
If a user tries to destroy the cm_id, the destruction will proceed,
under the incorrect assumption that no other threads are referencing
the cm_id. This can lead to a crash when the cm callback thread tries
to access the cm_id.
This problem was noticed as part of a larger investigation with kernel
crashes in the rdma_cm when running on a real time OS.
Signed-off-by: Sean Hefty<sean.hefty@intel.com>
Acked-by: Doug Ledford<dledford@redhat.com>
Cc:<stable@kernel.org>
Signed-off-by: Roland Dreier<roland@purestorage.com>
I'm a bit curious how you got these 2 patches to apply 'cause they were
released with 2.6.35-29.51. Did you start with master instead of
master-next ?
rtg
--
Tim Gardner tim.gardner@canonical.com
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
04-26-2011, 03:13 AM
Brad Figg
IB/cm: Bump reference count on cm_id before invoking callback, CVE-2011-0695
On 04/25/2011 05:53 PM, Tim Gardner wrote:
On 04/25/2011 01:29 PM, Brad Figg wrote:
From: Sean Hefty<sean.hefty@intel.com>
CVE-2011-0695
BugLink: http://bugs.launchpad.net/bugs/770369
When processing a SIDR REQ, the ib_cm allocates a new cm_id. The
refcount of the cm_id is initialized to 1. However, cm_process_work
will decrement the refcount after invoking all callbacks. The result
is that the cm_id will end up with refcount set to 0 by the end of the
sidr req handler.
If a user tries to destroy the cm_id, the destruction will proceed,
under the incorrect assumption that no other threads are referencing
the cm_id. This can lead to a crash when the cm callback thread tries
to access the cm_id.
This problem was noticed as part of a larger investigation with kernel
crashes in the rdma_cm when running on a real time OS.
Signed-off-by: Sean Hefty<sean.hefty@intel.com>
Acked-by: Doug Ledford<dledford@redhat.com>
Cc:<stable@kernel.org>
Signed-off-by: Roland Dreier<roland@purestorage.com>
I'm a bit curious how you got these 2 patches to apply 'cause they were released with 2.6.35-29.51. Did you start with master instead of master-next ?
rtg
That's a really good question. I patched an old local repo. I got distracted
working on these and thought I'd updated my repo but had not. Thanks for
catching this and sorry to waste everyone's time.