Description
In the Linux kernel, the following vulnerability has been resolved:

dibs: initialise dibs->lock in dibs_dev_alloc()

dibs->lock is initialised by dibs_dev_add(), but a dibs device can
already take interrupts before that call: ism_probe() runs
ism_dev_init(), and hence request_irq(), before it calls
dibs_dev_add(). No client can have registered a dmb at that point, so
no dmb interrupt can occur, but a GID event interrupt can, and
ism_handle_irq() takes dibs->lock unconditionally on entry, before it
inspects anything else.

Initialise the lock in dibs_dev_alloc() instead, so that it is valid as
soon as a driver can publish the device to its interrupt handler.
Published: 2026-08-22
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises from the Linux kernel's dibs device subsystem, where the lock used to protect dibs device data is not initialized when the device registers an interrupt handler. Because dibs_dev_alloc() allocates the device before the lock is set, an interrupt can occur before dibs_dev_add() initializes the lock. The interrupt handler, ism_handle_irq(), unconditionally acquires the uninitialized lock. This race can provoke undefined behavior, potentially leading to denial of service by crashing the kernel.

Affected Systems

Affected systems run the Linux kernel with the dibs device driver, which could be the ISM driver used for integrated silicon management. The CVE notes only a generic Linux kernel, with no specific version guidance, so any kernel containing the uninitialized lock code prior to the patch is at risk. The affected product is the Linux kernel; version information is not supplied.

Risk and Exploitability

No CVSS score or EPSS data is published, and the vulnerability is not listed in CISA KEV. Because the flaw hinges on low-level interrupt handling and requires a device capable of generating the specific GID events, the likelihood of exploitation in the wild is uncertain. However, an attacker with local or higher privileges who can trigger the relevant interrupts might cause a denial of service. The fix simply moves lock initialization into dibs_dev_alloc(), eliminating the race.

Generated by OpenCVE AI on August 22, 2026 at 17:16 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest kernel update that includes the dibs lock initialization fix.
  • Reboot the system after applying the update to ensure the fix is in place.
  • If an update is not immediately feasible, temporarily disable the ISM driver or GID event handling until an official patch is available.

Generated by OpenCVE AI on August 22, 2026 at 17:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 22 Aug 2026 17:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Sat, 22 Aug 2026 15:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dibs: initialise dibs->lock in dibs_dev_alloc() dibs->lock is initialised by dibs_dev_add(), but a dibs device can already take interrupts before that call: ism_probe() runs ism_dev_init(), and hence request_irq(), before it calls dibs_dev_add(). No client can have registered a dmb at that point, so no dmb interrupt can occur, but a GID event interrupt can, and ism_handle_irq() takes dibs->lock unconditionally on entry, before it inspects anything else. Initialise the lock in dibs_dev_alloc() instead, so that it is valid as soon as a driver can publish the device to its interrupt handler.
Title dibs: initialise dibs->lock in dibs_dev_alloc()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-22T15:32:02.049Z

Reserved: 2026-08-15T05:44:03.920Z

Link: CVE-2026-74617

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-22T16:16:34.400

Modified: 2026-08-22T16:16:34.400

Link: CVE-2026-74617

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-22T18:15:03Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')