n the Linux kernel, the following vulnerability has been resolved: spi: rockchip: Resolve unbalanced runtime PM / system PM handling Commit e882575efc77 ("spi: rockchip: Suspend and resume the bus during NOIRQ_SYSTEM_SLEEP_PM ops") stopped respecting runtime PM status and simply disabled clocks unconditionally when suspending the system. This causes problems when the device is already runtime suspended when we go to sleep -- in which case we double-disable clocks and produce a WARNing. Switch back to pm_runtime_force_{suspend,resume}(), because that still seems like the right thing to do, and the aforementioned commit makes no explanation why it stopped using it. Also, refactor some of the resume() error handling, because it's not actually a good idea to re-disable clocks on failure.
Configuration 1 (hide)
|
03 Nov 2025, 23:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
08 Oct 2024, 18:25
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://git.kernel.org/stable/c/0efbad8445fbba7896402500a1473450a299a08a - Patch | |
| References | () https://git.kernel.org/stable/c/14f970a8d03d882b15b97beb83bd84ac8ba6298c - Patch | |
| References | () https://git.kernel.org/stable/c/be721b451affbecc4ba4eaac3b71cdbdcade1b1b - Patch | |
| References | () https://git.kernel.org/stable/c/d034bff62faea1a2219e0d2f3d17263265f24087 - Patch | |
| CPE | cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:* |
|
| First Time |
Linux
Linux linux Kernel |
|
| CWE | NVD-CWE-noinfo | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
30 Sep 2024, 12:45
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
27 Sep 2024, 13:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Published : 2024-09-27 13:15
Updated : 2025-11-03 23:16
NVD link : CVE-2024-46846
Mitre link : CVE-2024-46846
CVE.ORG link : CVE-2024-46846
JSON object : View