In the Linux kernel, the following vulnerability has been resolved: dibs: initialise dibs->lock in dibs_dev_alloc() dibs->lock is initialised by… (CVE-2026-74617)
A vulnerability in the Linux kernel related to the initialization of the dibs->lock in the dibs device driver was resolved. The lock was previously initialized too late, after interrupts could already occur, potentially leading to unsafe lock usage. The fix involves initializing the lock earlier in the device allocation function to ensure it is valid before any interrupt handling begins.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's dibs device driver arises because dibs->lock was initialized in dibs_dev_add(), but interrupts could occur earlier during ism_probe() and ism_dev_init(), which call request_irq() before dibs_dev_add(). Since ism_handle_irq() takes dibs->lock unconditionally on entry, this could lead to using an uninitialized lock. The fix was to initialize dibs->lock in dibs_dev_alloc(), ensuring the lock is valid as soon as the device can receive interrupts.
Potential Impact
The issue could lead to unsafe lock usage in interrupt handling code, potentially causing race conditions or kernel instability. However, no client could have registered a dmb interrupt at that point, limiting the scope of interrupt-related issues to GID event interrupts. There are no known exploits in the wild for this vulnerability.
Mitigation Recommendations
A fix has been applied by initializing dibs->lock earlier in the device allocation process. Users should update to a Linux kernel version that includes this fix once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: dibs: initialise dibs->lock in dibs_dev_alloc() dibs->lock is initialised by… (CVE-2026-74617)
Description
A vulnerability in the Linux kernel related to the initialization of the dibs->lock in the dibs device driver was resolved. The lock was previously initialized too late, after interrupts could already occur, potentially leading to unsafe lock usage. The fix involves initializing the lock earlier in the device allocation function to ensure it is valid before any interrupt handling begins.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's dibs device driver arises because dibs->lock was initialized in dibs_dev_add(), but interrupts could occur earlier during ism_probe() and ism_dev_init(), which call request_irq() before dibs_dev_add(). Since ism_handle_irq() takes dibs->lock unconditionally on entry, this could lead to using an uninitialized lock. The fix was to initialize dibs->lock in dibs_dev_alloc(), ensuring the lock is valid as soon as the device can receive interrupts.
Potential Impact
The issue could lead to unsafe lock usage in interrupt handling code, potentially causing race conditions or kernel instability. However, no client could have registered a dmb interrupt at that point, limiting the scope of interrupt-related issues to GID event interrupts. There are no known exploits in the wild for this vulnerability.
Mitigation Recommendations
A fix has been applied by initializing dibs->lock earlier in the device allocation process. Users should update to a Linux kernel version that includes this fix once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-65j5-6jf7-5p7m
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74617"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f3acd9273b499bc892
Added to database: 08/22/2026, 22:51:31 UTC
Last enriched: 08/22/2026, 23:10:59 UTC
Last updated: 08/23/2026, 01:50:13 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.