Heimdall Security Logo

CVE-2026-43203

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.6%
Linux•Linux•Versions : <=6.1.*, <aba0b4bc09376dfc3d53c826514fe38fc8337f52, <=6.12.*, 2.6.12, 0, 7.0, <73fbc5d1a9ccb626937500bbd67136f077d8237b, 6.1.165, 6.12.75, <91f25749aaf57c47ae1e12478144e6ea8c8562f2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <2.6.12, <=5.10.*, <=6.6.*, <=6.19.*, <e075ec9b08f862dade8011481058f7eb5f716c57, <e4ff4e3ffcf9d5aad380cdd1d8cdc008bb34f97d, <=6.18.*, 6.19.6, 6.6.128, 5.10.252, <97900f512252a59f23d6ce4ab215cc88fed66e68, 6.18.16, <=*, <=5.15.*, <8930878101cd40063888a68af73b1b0f8b6c79bc, 5.15.202, <5189368f10903956be05062d160b2804bf5e5016

Description

In the Linux kernel, the following vulnerability has been resolved: atm: fore200e: fix use-after-free in tasklets during device removal When the PCA-200E or SBA-200E adapter is being detached, the fore200e is deallocated. However, the tx_tasklet or rx_tasklet may still be running or pending, leading to use-after-free bug when the already freed fore200e is accessed again in fore200e_tx_tasklet() or fore200e_rx_tasklet(). One of the race conditions can occur as follows: CPU 0 (cleanup) | CPU 1 (tasklet) fore200e_pca_remove_one() | fore200e_interrupt() fore200e_shutdown() | tasklet_schedule() kfree(fore200e) | fore200e_tx_tasklet() | fore200e-> // UAF Fix this by ensuring tx_tasklet or rx_tasklet is properly canceled before the fore200e is released. Add tasklet_kill() in fore200e_shutdown() to synchronize with any pending or running tasklets. Moreover, since fore200e_reset() could prevent further interrupts or data transfers, the tasklet_kill() should be placed after fore200e_reset() to prevent the tasklet from being rescheduled in fore200e_interrupt(). Finally, it only needs to do tasklet_kill() when the fore200e state is greater than or equal to FORE200E_STATE_IRQ, since tasklets are uninitialized in earlier states. In a word, the tasklet_kill() should be placed in the FORE200E_STATE_IRQ branch within the switch...case structure. This bug was identified through static analysis.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <aba0b4bc09376dfc3d53c826514fe38fc8337f52, <=6.12.*, 2.6.12, 0, 7.0, <73fbc5d1a9ccb626937500bbd67136f077d8237b, 6.1.165, 6.12.75, <91f25749aaf57c47ae1e12478144e6ea8c8562f2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <2.6.12, <=5.10.*, <=6.6.*, <=6.19.*, <e075ec9b08f862dade8011481058f7eb5f716c57, <e4ff4e3ffcf9d5aad380cdd1d8cdc008bb34f97d, <=6.18.*, 6.19.6, 6.6.128, 5.10.252, <97900f512252a59f23d6ce4ab215cc88fed66e68, 6.18.16, <=*, <=5.15.*, <8930878101cd40063888a68af73b1b0f8b6c79bc, 5.15.202, <5189368f10903956be05062d160b2804bf5e5016) 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

Rechercher une autre CVE