CVE-2025-68339

Bandwidth accounting corruption via unlocked VCC rollback

Published Dec 23, 2025 · Updated Dec 23, 2025

Race condition in the Linux fore200e ATM driver allows attackers to corrupt shared bandwidth accounting during failed VCC setup. In fore200e_open(), the failure path after fore200e_activate_vcin() adds reserved bandwidth back to available_cell_rate without rate_mtx, allowing a stale read-modify-write to overwrite a concurrent VCC update. Reachability requires a FORE Systems 200E-series ATM adapter and a failed activation concurrent with close or QoS activity; the reported consequence is incorrect accounting, not code execution.

CVSS severityUnavailable
Unscored
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in the Linux fore200e ATM driver allows attackers to corrupt shared bandwidth accounting during failed VCC setup. In fore200e_open(), the failure path after fore200e_activate_vcin() adds reserved bandwidth back to available_cell_rate without rate_mtx, allowing a stale read-modify-write to overwrite a concurrent VCC update. Reachability requires a FORE Systems 200E-series ATM adapter and a failed activation concurrent with close or QoS activity; the reported consequence is incorrect accounting, not code execution.

The record

CVE
CVE-2025-68339
Published
Dec 23, 2025
Updated
Dec 23, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Dec 23, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6610361458e7eb6502dd3182f586f91fcc218039
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <667ac868823224374f819500adc5baa2889c7bc5
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <82fca3d8a4a34667f01ec2351a607135249c9cff
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9917ba597cf95f307778e495f71ff25a5064d167
  6. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd1415efbab507b9b995918105eef953013449dd
  7. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1
  8. Affected versionversion=2.6.12

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b60f42a639999c37da7f1fbfa1ad29cf4cbdd2d; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6610361458e7eb6502dd3182f586f91fcc218039; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <667ac868823224374f819500adc5baa2889c7bc5; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <82fca3d8a4a34667f01ec2351a607135249c9cff; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9917ba597cf95f307778e495f71ff25a5064d167; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd1415efbab507b9b995918105eef953013449dd; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed34c70d88e2b8b9bc6c3ede88751186d6c6d5d1; version=2.6.12

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo