CVE-2025-68339
atm/fore200e: Fix possible data race in fore200e_open()
Reported by linux · Published December 23, 2025
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.
EPSS 0.19% · 8.8th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.18, 6.17.11, 6.12.61, 6.6.119, 6.1.159, 5.15.197, 5.10.247 |
| Linux | Linux | ed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1, bd1415efbab507b9b995918105eef953013449dd, 9917ba597cf95f307778e495f71ff25a5064d167, 82fca3d8a4a34667f01ec2351a607135249c9cff, 667ac868823224374f819500adc5baa2889c7bc5, 6610361458e7eb6502dd3182f586f91fcc218039, 1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| Linux | Linux | 2.6.12, 0, 5.10.247 |
| linux | linux_kernel | 2.6.12, 2.6.12, 2.6.12 |
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
Timeline
- Dec 23, 2025 CVE Published
- Dec 24, 2025 EPSS Score (30 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (66 in total, the first dated here)
- Mar 29, 2026 Security Advisory (70 in total, the first dated here)
- Jun 17, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68339
vulnetix vdb fixes CVE-2025-68339
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68339/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart