Answer in brief
CVE-2026-68233 records a Unknown severity vulnerability in drm/vc4: Shut down BO cache timer before teardown. 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c826a6e1064419f78855463cf29ce9e8b9d25bf4 <a38f2724eb93a78ba250b01e0caf3468df4d3956 || >=c826a6e1064419f78855463cf29ce9e8b9d25bf4 <bac4c1a9af690b8635c6924872075c41d8763ed9 || >=c826a6e1064419f78855463cf29ce9e8b9d25bf4 <6273dd3ffb54ec581855b82ae77331b66028249c | a38f2724eb93a78ba250b01e0caf3468df4d3956, bac4c1a9af690b8635c6924872075c41d8763ed9, 6273dd3ffb54ec581855b82ae77331b66028249c |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Shut down BO cache timer before teardown The BO cache timer callback schedules time_work, and time_work can rearm the timer through vc4_bo_cache_free_old(). vc4_bo_cache_destroy() deletes the timer and then cancels the work, which does not break that cycle: the work being cancelled can rearm the timer, and the timer then queues work again after teardown. Use timer_shutdown_sync() instead, so the timer cannot be rearmed and the cycle ends with cancel_work_sync().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68233 records a Unknown severity vulnerability in drm/vc4: Shut down BO cache timer before teardown. 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c826a6e1064419f78855463cf29ce9e8b9d25bf4 <a38f2724eb93a78ba250b01e0caf3468df4d3956 || >=c826a6e1064419f78855463cf29ce9e8b9d25bf4 <bac4c1a9af690b8635c6924872075c41d8763ed9 || >=c826a6e1064419f78855463cf29ce9e8b9d25bf4 <6273dd3ffb54ec581855b82ae77331b66028249c | a38f2724eb93a78ba250b01e0caf3468df4d3956, bac4c1a9af690b8635c6924872075c41d8763ed9, 6273dd3ffb54ec581855b82ae77331b66028249c |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Shut down BO cache timer before teardown The BO cache timer callback schedules time_work, and time_work can rearm the timer through vc4_bo_cache_free_old(). vc4_bo_cache_destroy() deletes the timer and then cancels the work, which does not break that cycle: the work being cancelled can rearm the timer, and the timer then queues work again after teardown. Use timer_shutdown_sync() instead, so the timer cannot be rearmed and the cycle ends with cancel_work_sync().
Quoted source text, attributed separately from HOL analysis.