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-2025-68339atm/fore200e: Fix possible data race in fore200e_open()

Description

In the Linux kernel, the following vulnerability has been resolved: atm/fore200e: Fix possible data race in fore200e_open() Protect access to fore200e->available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race. The field fore200e->available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos(). In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc->qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock. This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs. Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 5 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bd1415efbab507b9b995918105eef953013449dd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9917ba597cf95f307778e495f71ff25a5064d167
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 667ac868823224374f819500adc5baa2889c7bc5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6610361458e7eb6502dd3182f586f91fcc218039
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 82fca3d8a4a34667f01ec2351a607135249c9cff
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.247 – ≤ 5.10.*
    • unaffected 5.15.197 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.119 – ≤ 6.6.*
    • unaffected 6.12.61 – ≤ 6.12.*
    • unaffected 6.17.11 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .