Answer in brief
CVE-2025-40311 records a Unknown severity vulnerability in accel/habanalabs: support mapping cb with vmalloc-backed coherent memory. 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 | >=ac0ae6a96aa58eeba4aed97b12ef1dea8c5bf399 <8de421db5b1b2b37e9643ea7f6ade90fd756892d || >=ac0ae6a96aa58eeba4aed97b12ef1dea8c5bf399 <7ec8ac9f73d4a9438c2186768d6de27ace37531e || >=ac0ae6a96aa58eeba4aed97b12ef1dea8c5bf399 <d1dfe21a332d38a6a09658ec29a55940afb5fe36 || >=ac0ae6a96aa58eeba4aed97b12ef1dea8c5bf399 <73c7c2cdb442fc4160d2a2a4bfffbd162af06cb9 || >=ac0ae6a96aa58eeba4aed97b12ef1dea8c5bf399 <513024d5a0e34fd34247043f1876b6138ca52847 | 8de421db5b1b2b37e9643ea7f6ade90fd756892d, 7ec8ac9f73d4a9438c2186768d6de27ace37531e, d1dfe21a332d38a6a09658ec29a55940afb5fe36, 73c7c2cdb442fc4160d2a2a4bfffbd162af06cb9, 513024d5a0e34fd34247043f1876b6138ca52847 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Dec 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 22, 2026
In the Linux kernel, the following vulnerability has been resolved: accel/habanalabs: support mapping cb with vmalloc-backed coherent memory When IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return addresses from the vmalloc range. If such an address is mapped without VM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the VM_PFNMAP restriction. Fix this by checking for vmalloc addresses and setting VM_MIXEDMAP in the VMA before mapping. This ensures safe mapping and avoids kernel crashes. The memory is still driver-allocated and cannot be accessed directly by userspace.
Quoted source text, attributed separately from HOL analysis.