# CVE-2026-74617: dibs: initialise dibs->lock in dibs_dev_alloc()

> A race condition in the Linux kernel dibs driver allows a denial of service via an uninitialized lock accessed during interrupt handling.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74617, DEBIAN-CVE-2026-74617, GHSA-65j5-6jf7-5p7m, UBUNTU-CVE-2026-74617

## What is CVE-2026-74617?

CVE-2026-74617 is a critical vulnerability in Linux, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-74617?


## How do I fix CVE-2026-74617?

Apply the vendor's patch.

## Is CVE-2026-74617 being exploited?

There is no known exploitation of CVE-2026-74617 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74617 and fix it if it is affected.

What it is: CVE-2026-74617 is a critical vulnerability in Linux, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74617 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74617/ (Markdown: https://insights.sbomify.com/CVE-2026-74617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74617
- OSV: https://osv.dev/vulnerability/CVE-2026-74617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74617/
Summaries are generated and may contain mistakes; the official description above is the record.