CVE-2026-43203

atm: fore200e: fix use-after-free in tasklets during device removal

State
Published
Severity
7.5 High
Published
May 6, 2026
Updated
Aug 5, 2026
Reserved
May 1, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.5 HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 91f25749aaf57c47ae1e12478144e6ea8c8562f2Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 73fbc5d1a9ccb626937500bbd67136f077d8237bAffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before aba0b4bc09376dfc3d53c826514fe38fc8337f52Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before e075ec9b08f862dade8011481058f7eb5f716c57Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 97900f512252a59f23d6ce4ab215cc88fed66e68Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before e4ff4e3ffcf9d5aad380cdd1d8cdc008bb34f97dAffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 5189368f10903956be05062d160b2804bf5e5016Affected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 8930878101cd40063888a68af73b1b0f8b6c79bcAffected
LinuxLinux
  • 2.6.12Affected
  • before 2.6.12Not affected
  • 5.10.252 through 5.10.*Not affected
  • 5.15.202 through 5.15.*Not affected
  • 6.1.165 through 6.1.*Not affected
  • 6.6.128 through 6.6.*Not affected
  • 6.12.75 through 6.12.*Not affected
  • 6.18.16 through 6.18.*Not affected
  • 6.19.6 through 6.19.*Not affected
  • 7.0 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.