Answer in brief
CVE-2026-53084 records a Unknown severity vulnerability in bpf: return VMA snapshot from task_vma iterator. 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 | >=4ac4546821584736798aaa9e97da9f6eaf689ea3 <83b8802c034e843b83a3e1ef6f30cdd4e9ec291c || >=4ac4546821584736798aaa9e97da9f6eaf689ea3 <592226d138378601ae28eb890e2bbc23ec3600f7 || >=4ac4546821584736798aaa9e97da9f6eaf689ea3 <13860ca37b8df0b856ee1ce3bdbd7c327d5f53e8 || >=4ac4546821584736798aaa9e97da9f6eaf689ea3 <4cbee026db54cad39c39db4d356100cb133412b3 | 83b8802c034e843b83a3e1ef6f30cdd4e9ec291c, 592226d138378601ae28eb890e2bbc23ec3600f7, 13860ca37b8df0b856ee1ce3bdbd7c327d5f53e8, 4cbee026db54cad39c39db4d356100cb133412b3 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: return VMA snapshot from task_vma iterator Holding the per-VMA lock across the BPF program body creates a lock ordering problem when helpers acquire locks that depend on mmap_lock: vm_lock -> i_rwsem -> mmap_lock -> vm_lock Snapshot the VMA under the per-VMA lock in _next() via memcpy(), then drop the lock before returning. The BPF program accesses only the snapshot. The verifier only trusts vm_mm and vm_file pointers (see BTF_TYPE_SAFE_TRUSTED_OR_NULL in verifier.c). vm_file is reference- counted with get_file() under the lock and released via fput() on the next iteration or in _destroy(). vm_mm is already correct because lock_vma_under_rcu() verifies vma->vm_mm == mm. All other pointers are left as-is by memcpy() since the verifier treats them as untrusted.
Quoted source text, attributed separately from HOL analysis.