Strix
63.2K

CVE-2026-80881

Unknown

Last modified

CVE-2026-80881 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= cf76c78595ca87548ca5e45c862ac9e0949c4687, < a4eae1499c760949a93459d11390bd1fd823d31d; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < 4ab17e328522a4df5fe0f0dcf39098118b1feeaa; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < 5927acb3e2c99985a14adecd9d1b67ba191c622d; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < ecb3f9386f4353034caef77239473c627232db17; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < 61f7a5acb3bf8fc97dad78f54b1e8d0e1c819766; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < 0e389fc290c350c67591abf4c367119f4689f310; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < 9e7a057934cdd58e4cc94350bcfe5367bbee0f8e; >= cf76c78595ca87548ca5e45c862ac9e0949c4687, < 6371a07148ee979af22a9d6f4c277462953a9a4a; 01f93d5e36753fc4d06ec67f05ce78c9c6f2dd56; 65cbd1279f4b999d56a838344a30642db24cd215; 97e1db17bc1ef4c2e1789bc9323c7be44fba53f8; 6c150df9c2e80b5cf86f5a0d98beb7390ad63bfc; >= 4.4.204, < 4.5; >= 4.9.204, < 4.10; >= 4.14.157, < 4.15; >= 4.19.87, < 4.20
LinuxLinux4.20

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80881?
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.
How severe is CVE-2026-80881?
Severity scoring for CVE-2026-80881 is pending analysis.
How do I fix CVE-2026-80881?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80881?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST