{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68339 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68339 is a vulnerability in Linux, published on 23 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68339 and fix it if it is affected.\n\nWhat it is: CVE-2025-68339 is a vulnerability in Linux, published on 23 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68339 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68339/ (Markdown: https://insights.sbomify.com/CVE-2025-68339/index.md)","id":"CVE-2025-68339","markdown":"https://insights.sbomify.com/CVE-2025-68339/index.md","name":"CVE-2025-68339","record":{"aliases":["AZL-72980","BELL-CVE-2025-68339","DEBIAN-CVE-2025-68339","GHSA-p5pr-v4m5-r2vj","ROOT-OS-DEBIAN-12-CVE-2025-68339","ROOT-OS-DEBIAN-13-CVE-2025-68339","ROOT-OS-UBUNTU-2204-CVE-2025-68339","ROOT-OS-UBUNTU-2404-CVE-2025-68339","UBUNTU-CVE-2025-68339"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel ATM driver","requires_auth":"none","summary":"A race condition in the Linux kernel ATM fore200e driver allows concurrent access to shared bandwidth resources, potentially causing incorrect accounting and denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\natm/fore200e: Fix possible data race in fore200e_open()\n\nProtect access to fore200e-\u003eavailable_cell_rate with rate_mtx lock in the\nerror handling path of fore200e_open() to prevent a data race.\n\nThe field fore200e-\u003eavailable_cell_rate is a shared resource used to track\navailable bandwidth. It is concurrently accessed by fore200e_open(),\nfore200e_close(), and fore200e_change_qos().\n\nIn fore200e_open(), the lock rate_mtx is correctly held when subtracting\nvcc-\u003eqos.txtp.max_pcr from available_cell_rate to reserve bandwidth.\nHowever, if the subsequent call to fore200e_activate_vcin() fails, the\nfunction restores the reserved bandwidth by adding back to\navailable_cell_rate without holding the lock.\n\nThis introduces a race condition because available_cell_rate is a global\ndevice resource shared across all VCCs. If the error path in\nfore200e_open() executes concurrently with operations like\nfore200e_close() or fore200e_change_qos() on other VCCs, a\nread-modify-write race occurs.\n\nSpecifically, the error path reads the rate without the lock. If another\nCPU acquires the lock and modifies the rate (e.g., releasing bandwidth in\nfore200e_close()) between this read and the subsequent write, the error\npath will overwrite the concurrent update with a stale value. This results\nin incorrect bandwidth accounting.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"atm/fore200e: Fix possible data race in fore200e_open()","id":"CVE-2025-68339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"team: Move team device type change at the end of team_port_add","id":"CVE-2025-68340"},"packages":[],"prev":{"headline":"net: dsa: microchip: Don't free uninitialized ksz_irq","id":"CVE-2025-68338"},"products":["Linux"],"published":"2025-12-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A race condition in the Linux kernel ATM fore200e driver allows concurrent access to shared bandwidth resources, potentially causing incorrect accounting and denial of service.","url":"https://insights.sbomify.com/CVE-2025-68339/"}