Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain

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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 039bef30e320827bac8990c9f29d2a68cd8adb5f, 1f77e5cd563e6387fdf3bb714fcda36cd88ac5e7, 7acc0390e0dd7474c4451d05465a677d55ad4268.

Low priority for now. Upgrade to Linux Linux 039bef30e320827bac8990c9f29d2a68cd8adb5f, 1f77e5cd563e6387fdf3bb714fcda36cd88ac5e7, 7acc0390e0dd7474c4451d05465a677d55ad4268 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: ocfs2: fix kernel BUG in ocfs2_find_victim_chain syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl->cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel. To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true: 1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list) Either of them being true is indicative of the fact that there are no chains left for usage. This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.

—No exploit Fix available
Published
Jan 13, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 10th 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.2%

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-68771

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.16affected
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before 1f77e5cd563e6387fdf3bb714fcda36cd88ac5e7affected · git
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before d0fd1f732ea8063cecd07a3879b7d815c7ee71edaffected · git
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before b08a33d5f80efe6979a6e8f905c1a898910c21ddaffected · git
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before 96f1b074c98c20f55a3b23d2ab44d9fb0f619869affected · git
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before e24aedae71652d4119049f1fbef6532ccbe3966daffected · git
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before 7acc0390e0dd7474c4451d05465a677d55ad4268affected · git
    • ccd979bdbce9fba8412beb3f1de68a9d0171b12c and later · before 039bef30e320827bac8990c9f29d2a68cd8adb5faffected · git
    • before 2.6.16not affected · semver
    • 5.10.248 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.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-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-68768Jan 13, 2026 · inet: frags: flush pending skbs in fqdir_pre_exit()
    0Monitor
  • ← EarlierCVE-2025-68769Jan 13, 2026 · f2fs: fix return value of f2fs_recover_fsync_data()
    0Monitor
  • Later →CVE-2025-68772Jan 13, 2026 · f2fs: fix to avoid updating compression context during writeback
    0Monitor

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 Linux039bef30e320827bac8990c9f29d2a68cd8adb5fVendor (CNA)
Linux Linux1f77e5cd563e6387fdf3bb714fcda36cd88ac5e7Vendor (CNA)
Linux Linux7acc0390e0dd7474c4451d05465a677d55ad4268Vendor (CNA)
Linux Linux96f1b074c98c20f55a3b23d2ab44d9fb0f619869Vendor (CNA)
Linux Linuxb08a33d5f80efe6979a6e8f905c1a898910c21ddVendor (CNA)
Linux Linuxd0fd1f732ea8063cecd07a3879b7d815c7ee71edVendor (CNA)
Linux Linuxe24aedae71652d4119049f1fbef6532ccbe3966dVendor (CNA)
debian:linux6.1.162-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