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: <2025050125-CVE-2025-23144-d85a@gregkh>
Date: Thu,  1 May 2025 14:56:24 +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-23144: backlight: led_bl: Hold led_access lock when calling led_sysfs_disable()

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

backlight: led_bl: Hold led_access lock when calling led_sysfs_disable()

Lockdep detects the following issue on led-backlight removal:
  [  142.315935] ------------[ cut here ]------------
  [  142.315954] WARNING: CPU: 2 PID: 292 at drivers/leds/led-core.c:455 led_sysfs_enable+0x54/0x80
  ...
  [  142.500725] Call trace:
  [  142.503176]  led_sysfs_enable+0x54/0x80 (P)
  [  142.507370]  led_bl_remove+0x80/0xa8 [led_bl]
  [  142.511742]  platform_remove+0x30/0x58
  [  142.515501]  device_remove+0x54/0x90
  ...

Indeed, led_sysfs_enable() has to be called with the led_access
lock held.

Hold the lock when calling led_sysfs_disable().

The Linux kernel CVE team has assigned CVE-2025-23144 to this issue.


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

	Issue introduced in 5.6 with commit ae232e45acf9621f2c96b41ca3af006ac7552c33 and fixed in 6.6.88 with commit 1c82f5a393d8b9a5c1ea032413719862098afd4b
	Issue introduced in 5.6 with commit ae232e45acf9621f2c96b41ca3af006ac7552c33 and fixed in 6.12.24 with commit 61a5c565fd2442d3128f3bab5f022658adc3a4e6
	Issue introduced in 5.6 with commit ae232e45acf9621f2c96b41ca3af006ac7552c33 and fixed in 6.13.12 with commit 11d128f7eacec276c75cf4712880a6307ca9c885
	Issue introduced in 5.6 with commit ae232e45acf9621f2c96b41ca3af006ac7552c33 and fixed in 6.14.3 with commit b8ddf5107f53789448900f04fa220f34cd2f777e
	Issue introduced in 5.6 with commit ae232e45acf9621f2c96b41ca3af006ac7552c33 and fixed in 6.15-rc1 with commit 276822a00db3c1061382b41e72cafc09d6a0ec30

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-23144
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/video/backlight/led_bl.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/1c82f5a393d8b9a5c1ea032413719862098afd4b
	https://git.kernel.org/stable/c/61a5c565fd2442d3128f3bab5f022658adc3a4e6
	https://git.kernel.org/stable/c/11d128f7eacec276c75cf4712880a6307ca9c885
	https://git.kernel.org/stable/c/b8ddf5107f53789448900f04fa220f34cd2f777e
	https://git.kernel.org/stable/c/276822a00db3c1061382b41e72cafc09d6a0ec30

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ