CVE-2026-53106
Last modified
CVE-2026-53106 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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/
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53106?
How severe is CVE-2026-53106?
How do I fix CVE-2026-53106?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53101In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53102In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53103In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53104In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53105In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53107In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53108In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-53109In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5311A security flaw has been discovered in D-Link DNS-120, DNR-2…5.5
- CVE-2026-53110In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53111In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53106?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
