CVE-2025-68771 — ocfs2: fix kernel BUG in ocfs2_find_victim_chain
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < 1f77e5cd563e6387fdf3bb714fcda36cd88ac5e7≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < d0fd1f732ea8063cecd07a3879b7d815c7ee71ed≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < b08a33d5f80efe6979a6e8f905c1a898910c21dd≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < 96f1b074c98c20f55a3b23d2ab44d9fb0f619869≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < e24aedae71652d4119049f1fbef6532ccbe3966d≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < 7acc0390e0dd7474c4451d05465a677d55ad4268≥ ccd979bdbce9fba8412beb3f1de68a9d0171b12c and < 039bef30e320827bac8990c9f29d2a68cd8adb5fversion 2.6.16 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- git.kernel.org/stable/c/1f77e5cd563e6387fdf3bb714fcda36cd88ac5e7
- git.kernel.org/stable/c/b08a33d5f80efe6979a6e8f905c1a898910c21dd
- git.kernel.org/stable/c/039bef30e320827bac8990c9f29d2a68cd8adb5f
- git.kernel.org/stable/c/d0fd1f732ea8063cecd07a3879b7d815c7ee71ed
- git.kernel.org/stable/c/7acc0390e0dd7474c4451d05465a677d55ad4268
- git.kernel.org/stable/c/e24aedae71652d4119049f1fbef6532ccbe3966d
- git.kernel.org/stable/c/96f1b074c98c20f55a3b23d2ab44d9fb0f619869
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-68771 is "ocfs2: fix kernel BUG in ocfs2_find_victim_chain", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.