Skip to page content

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX vulnerability intelligence

CVE-2026-43203

HIGH · CVSS 7.5 · Analyzed

Published: 2026-05-06 · Updated: 2026-11-11 · Source: NVD

Stored catalog record

Source record retrieved 2026-11-11T22:14:04.051402+00:00. Scheduled imports handle updates; this page does not assert that the provider was queried just now.

Continue your research

Connect this record to stored reporting, reviewed campaign mentions and source-domain investigation. These are research leads, not inferred attack relationships.

Open CVE research in Investigate · Find Arsenal listings referencing this CVE

Vulnerability overview

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.

Patch review priority

Assess exposure and vendor guidance

  • No higher-priority signal is available in the current stored evidence.

FIRST EPSS: 0.40% · percentile 34.9 · score date 2026-11-18.

EPSS estimates probability of exploitation in the next 30 days. It does not measure your exposure or prove exploitation. The elevated threshold is 10%; CISA KEV takes precedence. About FIRST EPSS ↗

Severity and scoring

CVSS score
7.5 · HIGH
CVSS version
3.1
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses
CWE-416

CVSS measures technical severity; it does not establish whether this vulnerability is being exploited in your environment.

Known exploitation and remediation

Not listed in the CISA catalog retrieved for this record. This does not establish that exploitation has not occurred.

Verify affected versions and patch availability in the vendor advisory before making changes.

Affected products and versions

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 2.6.12.1

    Before (exclusive): 5.10.252

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 5.11

    Before (exclusive): 5.15.202

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 5.16

    Before (exclusive): 6.1.165

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.2

    Before (exclusive): 6.6.128

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.7

    Before (exclusive): 6.12.75

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.13

    Before (exclusive): 6.18.16

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.19

    Before (exclusive): 6.19.6

  • cpe:2.3:o:linux:linux_kernel:2.6.12:-:*:*:*:*:*:*

  • cpe:2.3:o:linux:linux_kernel:2.6.12:rc2:*:*:*:*:*:*

  • cpe:2.3:o:linux:linux_kernel:2.6.12:rc3:*:*:*:*:*:*

  • cpe:2.3:o:linux:linux_kernel:2.6.12:rc4:*:*:*:*:*:*

  • cpe:2.3:o:linux:linux_kernel:2.6.12:rc5:*:*:*:*:*:*

These are NVD CPE applicability entries. Some products depend on configuration conditions; consult the official record to confirm applicability.

Advisories and references

Explore official sources

Read the official NVD record ↗

Explore the CISA catalog ↗

Back to CVE intelligence