[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025071011-CVE-2025-38287-b0ff@gregkh>
Date: Thu, 10 Jul 2025 09:42:28 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38287: IB/cm: Drop lockdep assert and WARN when freeing old msg
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
IB/cm: Drop lockdep assert and WARN when freeing old msg
The send completion handler can run after cm_id has advanced to another
message. The cm_id lock is not needed in this case, but a recent change
re-used cm_free_priv_msg(), which asserts that the lock is held and
WARNs if the cm_id's currently outstanding msg is different than the one
being freed.
The Linux kernel CVE team has assigned CVE-2025-38287 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 1e5159219076ddb2e44338c667c83fd1bd43dfef and fixed in 6.15.3 with commit fc096a0cd2017cb0aa1e7fb83131410af9283910
Issue introduced in 6.13 with commit 1e5159219076ddb2e44338c667c83fd1bd43dfef and fixed in 6.16-rc1 with commit 7590649ee7af381a9d1153143026dec124c5798e
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-38287
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/infiniband/core/cm.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/fc096a0cd2017cb0aa1e7fb83131410af9283910
https://git.kernel.org/stable/c/7590649ee7af381a9d1153143026dec124c5798e
Powered by blists - more mailing lists