LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52589: media: rkisp1: Fix IRQ disable race issue

In the Linux kernel, the following vulnerability has been resolved: media: rkisp1: Fix IRQ disable race issue In rkisp1_isp_stop() and rkisp1_csi_disable() the driver masks the interrupts and then apparently assumes that the interrupt handler won't be running, and proceeds in the stop procedure. This is not the case, as the interrupt handler can already be running, which would lead to the ISP being disabled while the interrupt handler handling a captured frame. This brings up two issues: 1) the ISP could be powered off while the interrupt handler is still running and accessing registers, leading to board lockup, and 2) the interrupt handler code and the code that disables the streaming might do things that conflict. It is not clear to me if 2) causes a real issue, but 1) can be seen with a suitable delay (or printk in my case) in the interrupt handler, leading to board lockup.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the rkisp1 camera/ISP driver. When camera streaming is stopped, the driver may power down hardware while an interrupt handler is still using it. The documented impact is board lockup, so the main business risk is device availability on affected camera-enabled Linux systems.

Executive priority

Treat as targeted availability risk for affected Linux camera devices. Prioritize patching where device lockup could disrupt operations, field devices, or physical security workflows. For standard servers without the rkisp1 hardware path, urgency is lower based on available evidence.

Technical view

The race is in rkisp1_isp_stop() and rkisp1_csi_disable(). The driver masks interrupts but does not guarantee an already-running handler has finished. That can leave the interrupt handler accessing ISP registers after the ISP is disabled or powered off, causing lockup. Conflicting stream-stop behavior is suspected but not confirmed in the source.

Likely exposure

Exposure appears limited to Linux systems using the rkisp1 media driver and affected kernel versions listed by the CVE. This is more likely relevant to embedded, camera, or board-level deployments than general-purpose servers without this hardware path.

Exploitation context

The source does not report active exploitation, KEV listing, public exploit code, or remote attack mechanics. The described trigger is a timing race during camera/ISP shutdown, with lockup observed using added delay or logging in the interrupt handler.

Researcher notes

Evidence supports a kernel driver race and board lockup, not privilege escalation or remote compromise. Severity, CVSS, CWE, and exploitability details are absent from the bundle. The exact affected version ranges should be verified through Linux or distribution advisories before broad conclusions.

Mitigation direction

  • Apply vendor or Linux stable kernel updates containing the referenced fixes.
  • Check distribution advisories for the exact patched kernel package.
  • Prioritize affected embedded or camera-enabled devices using rkisp1.
  • If updates are unavailable, consult vendor guidance for driver or camera-path workarounds.

Validation and detection

  • Inventory kernels and confirm whether rkisp1 is present or enabled.
  • Map deployed kernel versions against the CVE affected-version data.
  • Confirm patched kernels include one of the referenced stable commits.
  • Regression-test camera start and stop flows on representative hardware.
Prepared
Confidence
medium
Sources
6

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-52589 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
5Source 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
LinuxLinux25cb42af9ffabffec499e9e69e2fd3797774ce5b, 25cb42af9ffabffec499e9e69e2fd3797774ce5b, 25cb42af9ffabffec499e9e69e2fd3797774ce5b, 25cb42af9ffabffec499e9e69e2fd3797774ce5bunaffected
LinuxLinux5.6, 0, 6.1.77, 6.6.16, 6.7.4, 6.8affected
Weakness

CWE details

No CWE listed

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