dibs: initialise dibs->lock in dibs_dev_alloc()

Answer in brief

CVE-2026-74617 records a Unknown severity vulnerability in dibs: initialise dibs->lock in dibs_dev_alloc(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 22, 2026Updated Aug 22, 2026Source checked Aug 22, 2026First seen by HOL Aug 22, 2026Material review Aug 22, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=cc21191b584c6f7836b0f10774f8278b7cbfba10 <fe79571f40434b257d68cbfb7b3ae93a794d8a11 \|\| >=cc21191b584c6f7836b0f10774f8278b7cbfba10 <2926031acba100d0c18fcfaa7a2ed29609318848 \|\| >=cc21191b584c6f7836b0f10774f8278b7cbfba10 <c27e360545373b7aee9862a5beef3b9fb3df0c25	fe79571f40434b257d68cbfb7b3ae93a794d8a11, 2926031acba100d0c18fcfaa7a2ed29609318848, c27e360545373b7aee9862a5beef3b9fb3df0c25
Linux/Linuxgeneric	6.18	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to fe79571f40434b257d68cbfb7b3ae93a794d8a11 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 22, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.