CVE-2026-63798

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.6.144, 5.15.211, 0, 3.12, <=7.1.*, <0405a65e4ebd9eac13a765f9f02ac05851ca5421, 5.10.260, <=5.10.*, <=6.6.*, 6.12.95, <44567537a2623dcd2b4018a7f043cf8069579e5d, <41826e5297e67cd96a0a46fde06a5069a8ce436a, <c2c7733101bb8c0b29ac9ee41073eaf602821a59, <37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057, b6ef9161e43ad58c3824bd76dc87716276f0cd70, <=6.18.*, 6.1.177, 6.18.38, <8176773dfceae7978b01c20b233693e072053700, <3.12, <=*, <83d7ec14b0938ad8cae008058fd6f912f4a9a312, <=5.15.*, 7.1.3, <b3a3831b2eb884641906fc5e46207b205b6aea13, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/imgpdc: Fix resource leak, add missing chained handler cleanup on remove The driver allocates domain generic chips using irq_alloc_domain_generic_chips() during probe and sets up chained handlers using irq_set_chained_handler_and_data(). However, on driver removal, the generic chips are not freed and the chained handlers are not removed. The generic chips remain on the global gc_list and may later be accessed by generic interrupt chip suspend, resume, or shutdown callbacks after the driver has been removed, potentially resulting in a use-after-free and kernel crash. The chained handlers that were installed in probe for peripheral and syswake interrupts are also left dangling, which can lead to spurious interrupts accessing freed memory. Fix these issues by: - Setting IRQ_DOMAIN_FLAG_DESTROY_GC flag in domain->flags, so the core code automatically removes generic chips when irq_domain_remove() is called - Clearing all chained handlers with NULL in pdc_intc_remove()

Gravité et risque d'exploitation

CVE-2026-63798 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.6.144, 5.15.211, 0, 3.12, <=7.1.*, <0405a65e4ebd9eac13a765f9f02ac05851ca5421, 5.10.260, <=5.10.*, <=6.6.*, 6.12.95, <44567537a2623dcd2b4018a7f043cf8069579e5d, <41826e5297e67cd96a0a46fde06a5069a8ce436a, <c2c7733101bb8c0b29ac9ee41073eaf602821a59, <37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057, b6ef9161e43ad58c3824bd76dc87716276f0cd70, <=6.18.*, 6.1.177, 6.18.38, <8176773dfceae7978b01c20b233693e072053700, <3.12, <=*, <83d7ec14b0938ad8cae008058fd6f912f4a9a312, <=5.15.*, 7.1.3, <b3a3831b2eb884641906fc5e46207b205b6aea13, 7.2) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références