LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46846: spi: rockchip: Resolve unbalanced runtime PM / system PM handling

In 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Rockchip SPI power management. During system suspend, an already runtime-suspended device can have clocks disabled twice, producing a kernel warning. The provided sources describe reliability/power-management fallout, not data exposure, privilege escalation, or remote compromise.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on the provided evidence. Patch affected Rockchip/Linux fleets through normal update channels, faster where device stability during suspend/resume is operationally important.

Technical view

The regression came from commit e882575efc77 changing Rockchip SPI suspend handling to disable clocks unconditionally during NOIRQ system sleep. If runtime PM had already suspended the device, suspend could double-disable clocks. The fix restores pm_runtime_force_suspend/resume behavior and adjusts resume error handling.

Likely exposure

Exposure appears limited to Linux kernels containing the affected Rockchip SPI driver change, especially systems using Rockchip-based hardware with SPI devices and suspend/resume behavior. Generic Linux systems without Rockchip SPI hardware are unlikely to be practically exposed.

Exploitation context

The source bundle does not support active exploitation: KEV is false, and the cited sources are kernel stable fixes and a Debian LTS advisory. No exploit technique, attacker path, or confirmed malicious use is described.

Researcher notes

Evidence points to a kernel power-management correctness bug in spi-rockchip. The bundle lacks CVSS, CWE, and exploitability detail. Validation should focus on affected kernel lineage, presence of Rockchip SPI, and whether downstream vendor kernels have backported the stable commits.

Mitigation direction

  • Update to a kernel containing the cited stable fixes.
  • For Debian LTS systems, follow the referenced Debian advisory.
  • Prioritize Rockchip-based embedded systems that use suspend/resume.
  • If no vendor package exists, track upstream kernel guidance.

Validation and detection

  • Inventory Linux kernel versions on Rockchip-based devices.
  • Confirm whether Rockchip SPI hardware and driver are present.
  • Check vendor changelogs for the cited stable fix commits.
  • Review suspend/resume logs for related kernel warnings.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-46846 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe882575efc771f130a24322377dc1033551da11d, e882575efc771f130a24322377dc1033551da11d, e882575efc771f130a24322377dc1033551da11d, e882575efc771f130a24322377dc1033551da11dunaffected
LinuxLinux5.18, 0, 6.1.110, 6.6.51, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.