blob: d4e018fd288efda98fcf6bddbd3af55b04ff55cc [file] [log] [blame]
From bippy-1.2.0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ima: Fix use-after-free on a dentry's dname.name
->d_name.name can change on rename and the earlier value can be freed;
there are conditions sufficient to stabilize it (->d_lock on dentry,
->d_lock on its parent, ->i_rwsem exclusive on the parent's inode,
rename_lock), but none of those are met at any of the sites. Take a stable
snapshot of the name instead.
The Linux kernel CVE team has assigned CVE-2024-39494 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 5.4.291 with commit 480afcbeb7aaaa22677d3dd48ec590b441eaac1a
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 5.10.235 with commit edf287bc610b18d7a9c0c0c1cb2e97b9348c71bb
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 5.15.174 with commit 0b31e28fbd773aefb6164687e0767319b8199829
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 6.1.97 with commit 7fb374981e31c193b1152ed8d3b0a95b671330d4
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 6.6.35 with commit dd431c3ac1fc34a9268580dd59ad3e3c76b32a8c
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 6.9.6 with commit a78a6f0da57d058e2009e9958fdcef66f165208c
Issue introduced in 3.7 with commit 2fe5d6def1672ae6635dd71867bf36dcfaa7434b and fixed in 6.10 with commit be84f32bb2c981ca670922e047cdde1488b233de
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-39494
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:
security/integrity/ima/ima_api.c
security/integrity/ima/ima_template_lib.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/480afcbeb7aaaa22677d3dd48ec590b441eaac1a
https://git.kernel.org/stable/c/edf287bc610b18d7a9c0c0c1cb2e97b9348c71bb
https://git.kernel.org/stable/c/0b31e28fbd773aefb6164687e0767319b8199829
https://git.kernel.org/stable/c/7fb374981e31c193b1152ed8d3b0a95b671330d4
https://git.kernel.org/stable/c/dd431c3ac1fc34a9268580dd59ad3e3c76b32a8c
https://git.kernel.org/stable/c/a78a6f0da57d058e2009e9958fdcef66f165208c
https://git.kernel.org/stable/c/be84f32bb2c981ca670922e047cdde1488b233de