Security readout for executives and security teams
Plain-English summary
CVE-2025-21688 is a Linux kernel bug in the Broadcom V3D graphics driver. A local user process can hit a timing race that dereferences a null job pointer and crashes the kernel. The cited impact is availability loss, not data theft or privilege escalation.
Executive priority
Treat this as a targeted availability issue, not a broad emergency. Patch affected Linux GPU systems in normal security maintenance, faster for shared, kiosk, lab, or multi-user devices where local users can run graphics workloads.
Technical view
The flaw is a CWE-362 race between the DRM scheduler workqueue and V3D IRQ handling. The IRQ path signaled a fence before clearing job state safely, allowing a new job assignment to race with NULL assignment. Later interrupt handling can dereference NULL in v3d_irq and trigger a kernel oops.
Likely exposure
Exposure is most likely on Linux systems using the v3d DRM driver, such as Raspberry Pi-class Broadcom V3D GPU platforms. The CVSS vector is local, high complexity, low privilege, no user interaction, with high availability impact only.
Exploitation context
The source bundle does not show KEV listing or active exploitation. Exploitation requires local access and successful timing of a race in GPU job completion and interrupt handling. Public evidence supports crash/denial-of-service risk, not remote compromise.
Researcher notes
The provided evidence is kernel-resolution text, stable commit references, and Debian LTS advisories. It identifies the race and crash path but does not provide proof of exploitation in the wild, exploit maturity, or non-Linux downstream product status.
Mitigation direction
Update to a vendor kernel containing the referenced stable V3D fix.
Apply Debian LTS kernel updates where those advisories apply.
Prioritize systems exposing local GPU workloads to untrusted users.
If updates are delayed, review vendor guidance for V3D driver risk reduction.
Validation and detection
Inventory Linux hosts using the v3d kernel module.
Compare running kernel packages against vendor advisories and stable commits.
Review kernel logs for v3d_irq NULL dereference oops signatures.
Confirm updated kernels boot and retain expected graphics functionality.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.