LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53573: clk: rs9: Fix suspend/resume

In the Linux kernel, the following vulnerability has been resolved: clk: rs9: Fix suspend/resume Disabling the cache in commit 2ff4ba9e3702 ("clk: rs9: Fix I2C accessors") without removing cache synchronization in resume path results in a kernel panic as map->cache_ops is unset, due to REGCACHE_NONE. Enable flat cache again to support resume again. num_reg_defaults_raw is necessary to read the cache defaults from hardware. Some registers are strapped in hardware and cannot be provided in software.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53573 is a Linux kernel reliability bug in the rs9 clock driver. On affected systems, suspend and resume can trigger a kernel panic because resume tries to synchronize a disabled register cache. This is most relevant to devices using the affected driver and hardware, not a broad internet-facing service issue.

Executive priority

Treat this as targeted operational reliability risk until vendor severity is clarified. Prioritize patch validation for Linux devices that depend on suspend/resume and rs9 clock hardware, especially embedded or appliance fleets where kernel panics cause service disruption.

Technical view

The bug was introduced when commit 2ff4ba9e3702 disabled regmap caching for the rs9 clock driver while leaving resume-time cache synchronization in place. With REGCACHE_NONE, map->cache_ops is unset, causing a panic. The kernel fix re-enables flat cache and uses num_reg_defaults_raw for hardware-derived register defaults.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or downstream kernels carrying the faulty rs9 clk driver change, with rs9-compatible hardware and suspend/resume behavior. The source bundle does not identify affected distributions, appliances, cloud images, or remotely reachable attack surfaces.

Exploitation context

No active exploitation is stated in the supplied sources, and this CVE is not marked KEV. The sources describe a kernel panic during resume, but do not provide evidence of remote exploitability, privilege escalation, public exploit code, or weaponization.

Researcher notes

The source data has no CVSS, CWE, or exploitability detail. Version data mixes commit IDs and kernel release ranges, so validate against actual downstream kernel trees. The fix direction is clear from stable commits: restore flat regcache support for resume synchronization.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check distribution or device vendor advisories for backported kernel packages.
  • Prioritize systems using rs9 clock hardware and suspend/resume workflows.
  • If patching is delayed, review vendor guidance for operational workarounds.

Validation and detection

  • Inventory kernel versions and downstream patch levels on relevant Linux systems.
  • Confirm whether the rs9 clock driver and matching hardware are present.
  • Verify the fixed stable commit is included or backported.
  • Regression test suspend and resume on representative affected hardware.
  • Review kernel logs for resume-time panics involving regmap or clk rs9.
Prepared
Confidence
medium
Sources
5

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-2023-53573 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
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2ff4ba9e37024735f5cefc5ea2a73fc66addfe0e, 2ff4ba9e37024735f5cefc5ea2a73fc66addfe0e, 2ff4ba9e37024735f5cefc5ea2a73fc66addfe0e, 94c9e0e11a53e18fcedbf4563ef04a07385b2c89, 6.0.8unaffected
LinuxLinux6.1, 0, 6.1.25, 6.2.12, 6.3affected
Weakness

CWE details

No CWE listed

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