ocfs2: fix buffer head management in ocfs2_read_blocks()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cf76c78595ca87548ca5e45c862ac9e0949c4687 · < 0e389fc290c350c67591abf4c367119f4689f310| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s OCFS2 block-read path can retain a buffer marked up to date after validation detects inconsistent data. A later read may place that buffer in the OCFS2 metadata cache and pass it to upper layers. The input does not specify an attacker route, authentication requirement, or user interaction.
Engineers running Linux systems that use OCFS2 should check their kernel versions; affected versions are not specified.