LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35953: accel/ivpu: Fix deadlock in context_xa

In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix deadlock in context_xa ivpu_device->context_xa is locked both in kernel thread and IRQ context. It requires XA_FLAGS_LOCK_IRQ flag to be passed during initialization otherwise the lock could be acquired from a thread and interrupted by an IRQ that locks it for the second time causing the deadlock. This deadlock was reported by lockdep and observed in internal tests.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-35953 is a Linux kernel deadlock issue in the accel/ivpu driver. The bug can occur when the same context lock is taken from normal kernel thread execution and interrupt context. The source reports detection by lockdep and internal testing, with no cited evidence of active exploitation.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize affected systems that use the ivpu driver and require high availability, then handle through normal kernel patch governance.

Technical view

The ivpu_device context_xa xarray is accessed from both kernel thread and IRQ contexts. Without XA_FLAGS_LOCK_IRQ during initialization, an interrupt can re-enter the same lock while it is held, causing a deadlock. The provided Linux stable commit references identify the resolved kernel changes.

Likely exposure

Exposure appears limited to systems running affected Linux kernel versions with the accel/ivpu driver present or in use. The source lists Linux versions including 6.3, 6.6.28, 6.8.7, and 6.9 as affected, but distro backport status is not provided.

Exploitation context

The source bundle does not show KEV listing, public exploitation, exploit availability, or attacker prerequisites. Evidence points to a reliability flaw found by kernel lock analysis and internal tests, not a confirmed in-the-wild campaign.

Researcher notes

The key condition is lock use across thread and IRQ context without XA_FLAGS_LOCK_IRQ. The available evidence is narrow: affected kernel versions and stable commit references are provided, but no CVSS, CWE, exploitability analysis, or distro-specific package mapping is included.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2024-35953 backport status.
  • Upgrade to a kernel containing the referenced stable fixes where applicable.
  • Prioritize systems using the accel/ivpu driver or related accelerator hardware.
  • Track maintenance windows for uptime-sensitive systems before kernel rollout.

Validation and detection

  • Inventory running Linux kernel versions across affected fleets.
  • Check whether the accel/ivpu driver is built, loaded, or used.
  • Confirm the deployed kernel includes the referenced stable fix commits or distro backport.
  • Review kernel logs for ivpu deadlock or lockdep reports.
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-2024-35953 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
4Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux35b137630f08d913fc2e33df33ccc2570dff3f7d, 35b137630f08d913fc2e33df33ccc2570dff3f7d, 35b137630f08d913fc2e33df33ccc2570dff3f7dunaffected
LinuxLinux6.3, 0, 6.6.28, 6.8.7, 6.9affected
Weakness

CWE details

No CWE listed

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