> CVE-2026-53106

« BACK_TO_HOME
PUBLISHED
2026-06-24 17:17
MODIFIED
2026-06-24 17:17
EPSS (Prob. Exploit)
0.14%
Top 96.7%
DATA SOURCES:
NVD 🔗 2026-06-24 RED HAT 🔗 2026-06-28 FIRST EPSS 🔗 2026-10-25 MSRC 🔗 2026-11-02

> 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/[email protected]/

> AFFECTED_PRODUCTS

ℹ️ Aucun produit affecté n'a encore été publié par NVD pour cette CVE.

> RED HAT SEVERITY ASSESSMENT

THREAT SEVERITY
Low

> HISTORIQUE DES MODIFICATIONS

Première apparition
24/06/2026 17:17
Source: NVD
📊 ENRICHISSEMENT 28/06/2026 05:02
REDHAT
Champ modifié: Sévérité Red Hat
Ancienne valeur:
N/A
Nouvelle valeur:
{ "threat_severity": "Low", "severity_scale": null }
📊 ENRICHISSEMENT 28/06/2026 05:02
REDHAT
Champ modifié: Red Hat
Ancienne valeur:
Non
Nouvelle valeur:
Oui
Total des modifications: 2 Dernière mise à jour: 4 months ago

> REFERENCES

https://git.kernel.org/stable/c/350de5b8a9befaa2a68861c51f671d4f5f751ca5
https://git.kernel.org/stable/c/e84acaf936970b5b0be2c93bbf255295ba9406df
« BACK_TO_HOME