Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68339: atm/fore200e: Fix possible data race in fore200e_open()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d, 6610361458e7eb6502dd3182f586f91fcc218039, 667ac868823224374f819500adc5baa2889c7bc5; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.

Low priority for now. Upgrade to Linux Linux 1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d, 6610361458e7eb6502dd3182f586f91fcc218039, 667ac868823224374f819500adc5baa2889c7bc5; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 23, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68339

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2daffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before bd1415efbab507b9b995918105eef953013449ddaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9917ba597cf95f307778e495f71ff25a5064d167affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 667ac868823224374f819500adc5baa2889c7bc5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6610361458e7eb6502dd3182f586f91fcc218039affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 82fca3d8a4a34667f01ec2351a607135249c9cffaffected · git
    • before 2.6.12not affected · semver
    • 5.10.247 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.11-16.17.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68337Dec 22, 2025 · jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted
    30Monitor
  • ← EarlierCVE-2025-68338Dec 23, 2025 · net: dsa: microchip: Don't free uninitialized ksz_irq
    0Monitor
  • Later →CVE-2025-68341Dec 23, 2025 · veth: reduce XDP no_direct return section to fix race
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2dVendor (CNA)
Linux Linux6610361458e7eb6502dd3182f586f91fcc218039Vendor (CNA)
Linux Linux667ac868823224374f819500adc5baa2889c7bc5Vendor (CNA)
Linux Linux82fca3d8a4a34667f01ec2351a607135249c9cffVendor (CNA)
Linux Linux9917ba597cf95f307778e495f71ff25a5064d167Vendor (CNA)
Linux Linuxbd1415efbab507b9b995918105eef953013449ddVendor (CNA)
Linux Linuxed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1Vendor (CNA)
azl3 kernel 6.6.117.1-1 on Azure Linux 3.06.6.119.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records