[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025011121-CVE-2024-48876-da61@gregkh>
Date: Sat, 11 Jan 2025 13:25:26 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-48876: stackdepot: fix stack_depot_save_flags() in NMI context
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
stackdepot: fix stack_depot_save_flags() in NMI context
Per documentation, stack_depot_save_flags() was meant to be usable from
NMI context if STACK_DEPOT_FLAG_CAN_ALLOC is unset. However, it still
would try to take the pool_lock in an attempt to save a stack trace in the
current pool (if space is available).
This could result in deadlock if an NMI is handled while pool_lock is
already held. To avoid deadlock, only try to take the lock in NMI context
and give up if unsuccessful.
The documentation is fixed to clearly convey this.
The Linux kernel CVE team has assigned CVE-2024-48876 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit 4434a56ec20925333d6cf4d4093641d063abd35b and fixed in 6.12.5 with commit 9bfeeeff2c92b9dd261198b601b45bde4c529841
Issue introduced in 6.8 with commit 4434a56ec20925333d6cf4d4093641d063abd35b and fixed in 6.13-rc2 with commit 031e04bdc834cda3b054ef6b698503b2b97e8186
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-2024-48876
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:
include/linux/stackdepot.h
lib/stackdepot.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/9bfeeeff2c92b9dd261198b601b45bde4c529841
https://git.kernel.org/stable/c/031e04bdc834cda3b054ef6b698503b2b97e8186
Powered by blists - more mailing lists