CVE-2026-53106
- Source
- https://cve.org/CVERecord?id=CVE-2026-53106
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-53106.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-53106
- Downstream
- Related
- Published
- 2026-06-24T16:30:41Z
- Modified
- 2026-08-31T18:26:59Z
- Summary
- bpf: Do not allow deleting local storage in NMI
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
bpf: Do not allow deleting local storage in NMI
Currently, local storage may deadlock when deferring freeing selem or local storage through kfree_rcu(), call_rcu() or call_rcu_tasks_trace() in NMI or reentrant. Since deleting selem in NMI is an unlikely use case, partially mitigate it by returning error when calling from bpf_xxx_storage_delete() helpers in NMI. Note that, it is still possible to deadlock through reentrant. A full mitigation requires returning error when irqs_disabled() is true, which, however is too heavy-handed for bpf_xxx_storage_delete().
The long-term solution requires _nolock versions of call_rcu. Another possible solution is to defer the free through irq_work [0], but it would grow the size of selem, which is non-ideal.
The check is only needed in bpf_selem_unlink(), which is used by helpers and syscalls. bpf_selem_unlink_nofail() is fine as it is called during map and owner tear down that never run in NMI or reentrant.
[0] https://lore.kernel.org/bpf/20260205190233.912-1-alexei.starovoitov@gmail.com/
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53106.json" }- References
-
- https://git.kernel.org/stable/c/350de5b8a9befaa2a68861c51f671d4f5f751ca5
- https://git.kernel.org/stable/c/e84acaf936970b5b0be2c93bbf255295ba9406df
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53106.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-53106
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git