Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43203, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.5CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.40% · top 65% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 91f25749aaf57c47ae1e12478144e6ea8c8562f2
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 73fbc5d1a9ccb626937500bbd67136f077d8237b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < aba0b4bc09376dfc3d53c826514fe38fc8337f52
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e075ec9b08f862dade8011481058f7eb5f716c57
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 97900f512252a59f23d6ce4ab215cc88fed66e68
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e4ff4e3ffcf9d5aad380cdd1d8cdc008bb34f97d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5189368f10903956be05062d160b2804bf5e5016
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8930878101cd40063888a68af73b1b0f8b6c79bc
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43203 badge
[![CVE-2026-43203](https://cveledger.app/badge/CVE-2026-43203.svg)](https://cveledger.app/cve/CVE-2026-43203)

Record last updated .