CVE-2026-43203

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

HIGH
7.5
CVSS Score
Published: May 6, 2026 at 11:28 AM UTC
Updated: August 5, 2026 at 01:24 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2522.6.12 ≤ v < 5.15.2022.6.12 ≤ v < 6.1.1652.6.12 ≤ v < 6.12.752.6.12 ≤ v < 6.18.162.6.12 ≤ v < 6.19.62.6.12 ≤ v < 6.6.1282.6.12 ≤ v < 7.02.6.12.1 ≤ v < 5.10.2525.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.166.19 ≤ v < 6.19.66.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.751da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.122.6.12 rc22.6.12 rc32.6.12 rc42.6.12 rc5
Vendor states this is fixed in 5189368f10903956be05062d160b2804bf5e5016 (fixed)
Vendor states this is fixed in 73fbc5d1a9ccb626937500bbd67136f077d8237b (fixed)
Vendor states this is fixed in 8930878101cd40063888a68af73b1b0f8b6c79bc (fixed)
Vendor states this is fixed in 91f25749aaf57c47ae1e12478144e6ea8c8562f2 (fixed)
Vendor states this is fixed in 97900f512252a59f23d6ce4ab215cc88fed66e68 (fixed)
Vendor states this is fixed in aba0b4bc09376dfc3d53c826514fe38fc8337f52 (fixed)
Vendor states this is fixed in e075ec9b08f862dade8011481058f7eb5f716c57 (fixed)
Vendor states this is fixed in e4ff4e3ffcf9d5aad380cdd1d8cdc008bb34f97d (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.252 (unaffected)
Vendor states this is fixed in 5.15.202 (unaffected)
Vendor states this is fixed in 6.1.165 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.16 (unaffected)
Vendor states this is fixed in 6.19.6 (unaffected)
Vendor states this is fixed in 6.6.128 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card