linux-cve-announce - CVE-2024-43830: leds: trigger: Unregister sysfs attributes before calling deactivate()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2024081727-CVE-2024-43830-3b85@gregkh>
Date: Sat, 17 Aug 2024 11:22:34 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-43830: leds: trigger: Unregister sysfs attributes before calling deactivate()

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

leds: trigger: Unregister sysfs attributes before calling deactivate()

Triggers which have trigger specific sysfs attributes typically store
related data in trigger-data allocated by the activate() callback and
freed by the deactivate() callback.

Calling device_remove_groups() after calling deactivate() leaves a window
where the sysfs attributes show/store functions could be called after
deactivation and then operate on the just freed trigger-data.

Move the device_remove_groups() call to before deactivate() to close
this race window.

This also makes the deactivation path properly do things in reverse order
of the activation path which calls the activate() callback before calling
device_add_groups().

The Linux kernel CVE team has assigned CVE-2024-43830 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 4.19 with commit a7e7a3156300 and fixed in 6.1.103 with commit 734ba6437e80
	Issue introduced in 4.19 with commit a7e7a3156300 and fixed in 6.6.44 with commit cb8aa9d2a4c8
	Issue introduced in 4.19 with commit a7e7a3156300 and fixed in 6.10.3 with commit 0788a6f3523d
	Issue introduced in 4.19 with commit a7e7a3156300 and fixed in 6.11-rc1 with commit c0dc9adf9474

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-43830
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/leds/led-triggers.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/734ba6437e80dfc780e9ee9d95f912392d12b5ea
	https://git.kernel.org/stable/c/cb8aa9d2a4c8a15d6a43ccf901ef3d094aa60374
	https://git.kernel.org/stable/c/0788a6f3523d3686a9eed5ea1e6fcce6841277b2
	https://git.kernel.org/stable/c/c0dc9adf9474ecb7106e60e5472577375aedaed3