CVE-2026-80881 — ocfs2: fix buffer head management in ocfs2_read_blocks()
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix buffer head management in ocfs2_read_blocks() In ocfs2_read_blocks(), caller should't assume that buffer head returned by 'sb_getblk()' is exclusively owned and so 'put_bh()' always drops b_count from 1 to 0. If it is not so, buffer head remains on hold and likely to be returned by the next call to 'sb_getblk()' unchanged - that is, with BH_Uptodate bit set even if it has failed validation previously, thus allowing to insert that buffer head into OCFS2 metadata cache and submit it to upper layers. To avoid such a scenario, BH_Uptodate should be cleared immediately after 'validate()' callback has detected some data inconsistency.
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 |
version 01f93d5e36753fc4d06ec67f05ce78c9c6f2dd56version 4.20≥ 4.19.87 and < 4.20≥ 4.14.157 and < 4.15≥ 4.9.204 and < 4.10≥ 4.4.204 and < 4.5version 6c150df9c2e80b5cf86f5a0d98beb7390ad63bfcversion 97e1db17bc1ef4c2e1789bc9323c7be44fba53f8 and 9 moreversion 65cbd1279f4b999d56a838344a30642db24cd215≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < a4eae1499c760949a93459d11390bd1fd823d31d≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < 6371a07148ee979af22a9d6f4c277462953a9a4a≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < 9e7a057934cdd58e4cc94350bcfe5367bbee0f8e≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < 0e389fc290c350c67591abf4c367119f4689f310≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < 61f7a5acb3bf8fc97dad78f54b1e8d0e1c819766≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < ecb3f9386f4353034caef77239473c627232db17≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < 5927acb3e2c99985a14adecd9d1b67ba191c622d≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 and < 4ab17e328522a4df5fe0f0dcf39098118b1feeaa |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 25, 2026 · 10 reading(s) · max 0.22%
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 · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/a4eae1499c760949a93459d11390bd1fd823d31d
- git.kernel.org/stable/c/4ab17e328522a4df5fe0f0dcf39098118b1feeaa
- git.kernel.org/stable/c/ecb3f9386f4353034caef77239473c627232db17
- git.kernel.org/stable/c/5927acb3e2c99985a14adecd9d1b67ba191c622d
- git.kernel.org/stable/c/0e389fc290c350c67591abf4c367119f4689f310
- git.kernel.org/stable/c/9e7a057934cdd58e4cc94350bcfe5367bbee0f8e
- git.kernel.org/stable/c/6371a07148ee979af22a9d6f4c277462953a9a4a
- git.kernel.org/stable/c/61f7a5acb3bf8fc97dad78f54b1e8d0e1c819766
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 10h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 10h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 10h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 10h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 10h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 10h
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-2026-80881 is "ocfs2: fix buffer head management in ocfs2_read_blocks()", 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.22% 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.