CVE-2026-80881

ocfs2: fix buffer head management in ocfs2_read_blocks()

N/A

Published: September 4, 2026 at 04:49 PM UTC

Updated: September 4, 2026 at 05:36 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 4.14.157v ≥ 4.19.87v ≥ 4.4.204v ≥ 4.9.2044.14.157 ≤ v < 4.154.19.87 ≤ v < 4.204.20 ≤ v < 5.10.2614.20 ≤ v < 5.15.2124.20 ≤ v < 6.1.1784.20 ≤ v < 6.12.974.20 ≤ v < 6.18.404.20 ≤ v < 6.6.1454.20 ≤ v < 7.1.54.20 ≤ v < 7.24.4.204 ≤ v < 4.54.9.204 ≤ v < 4.101f93d5e36753fc4d6ec67f5ce78c9c6f2dd564.14.157 4.19.87 4.20 4.4.204 4.9.20465cbd1279f4b999d56a838344a30642db24cd2156c150df9c2e80b5cf86f5a0d98beb7390ad63bfc97e1db17bc1ef4c2e1789bc9323c7be44fba53f8cf76c78595ca87548ca5e45c862ac9e0949c4687

Vendor states this is fixed in 0e389fc290c350c67591abf4c367119f4689f310 (fixed)

Vendor states this is fixed in 4ab17e328522a4df5fe0f0dcf39098118b1feeaa (fixed)

Vendor states this is fixed in 5927acb3e2c99985a14adecd9d1b67ba191c622d (fixed)

Vendor states this is fixed in 61f7a5acb3bf8fc97dad78f54b1e8d0e1c819766 (fixed)

Vendor states this is fixed in 6371a07148ee979af22a9d6f4c277462953a9a4a (fixed)

Vendor states this is fixed in 9e7a057934cdd58e4cc94350bcfe5367bbee0f8e (fixed)

Vendor states this is fixed in a4eae1499c760949a93459d11390bd1fd823d31d (fixed)

Vendor states this is fixed in ecb3f9386f4353034caef77239473c627232db17 (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.20 (unaffected)

Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement