CVE-2025-68339 Details
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.
A data race vulnerability has been identified in the Linux kernel's ATM fore200e driver, specifically in the fore200e_open() function. This vulnerability arises from improper handling of the available_cell_rate variable, which tracks bandwidth and is accessed concurrently by multiple functions. The issue occurs when fore200e_open() reserves bandwidth by updating available_cell_rate without holding the necessary lock. If an error occurs and the function attempts to restore the bandwidth while another process is modifying the same variable, it can lead to incorrect bandwidth calculations. This vulnerability affects the Linux kernel stable group.
The vulnerability has been addressed by modifying the fore200e_open() function to ensure that the rate_mtx lock is applied during the entire bandwidth reservation process, including error handling. Users should update to the latest version of the Linux kernel where this fix has been implemented.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 23, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/6610361458e7eb6502dd3182f586f91fcc218039 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/667ac868823224374f819500adc5baa2889c7bc5 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/82fca3d8a4a34667f01ec2351a607135249c9cff | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/9917ba597cf95f307778e495f71ff25a5064d167 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/bd1415efbab507b9b995918105eef953013449dd | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
| ATM Fore200e | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 23, 2025 | New CVE Received | kernel.org |
Volerion