0.0
NA
CVE-2026-74617
dibs: initialise dibs->lock in dibs_dev_alloc()
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.

INFO

Published Date :

Aug. 22, 2026, 4:16 p.m.

Last Modified :

Aug. 22, 2026, 4:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-74617 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Initialize the lock earlier in the device allocation process to prevent race conditions.
  • Initialize dibs->lock in dibs_dev_alloc().
  • Ensure lock is valid before interrupt handler access.
  • Apply the provided patch to the Linux kernel.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-74617.

URL Resource
https://git.kernel.org/stable/c/2926031acba100d0c18fcfaa7a2ed29609318848
https://git.kernel.org/stable/c/c27e360545373b7aee9862a5beef3b9fb3df0c25
https://git.kernel.org/stable/c/fe79571f40434b257d68cbfb7b3ae93a794d8a11
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-74617 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-74617 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-74617 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-74617 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 22, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'cc21191b584c6f7836b0f10774f8278b7cbfba10', 'lessThan': 'fe79571f40434b257d68cbfb7b3ae93a794d8a11', 'versionType': 'git'}, {'status': 'affected', 'version': 'cc21191b584c6f7836b0f10774f8278b7cbfba10', 'lessThan': '2926031acba100d0c18fcfaa7a2ed29609318848', 'versionType': 'git'}, {'status': 'affected', 'version': 'cc21191b584c6f7836b0f10774f8278b7cbfba10', 'lessThan': 'c27e360545373b7aee9862a5beef3b9fb3df0c25', 'versionType': 'git'}], 'programFiles': ['drivers/dibs/dibs_main.c', 'include/linux/dibs.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.18'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.18', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.45', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.9', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/dibs/dibs_main.c', 'include/linux/dibs.h'], 'defaultStatus': 'affected'}]
    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.
    Added Reference https://git.kernel.org/stable/c/2926031acba100d0c18fcfaa7a2ed29609318848
    Added Reference https://git.kernel.org/stable/c/c27e360545373b7aee9862a5beef3b9fb3df0c25
    Added Reference https://git.kernel.org/stable/c/fe79571f40434b257d68cbfb7b3ae93a794d8a11
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.