https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 21:32:35 +0000 https://cve.radiocsirt.org/vuln/cve-2026-80881 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ocfs2: fix buffer head management in ocfs2_read_blocks()</p> <p>In ocfs2_read_blocks(), caller should&#39;t assume that buffer head returned by &#39;sb_getblk()&#39; is exclusively owned and so &#39;put_bh()&#39; 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 &#39;sb_getblk()&#39; 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 &#39;validate()&#39; callback has detected some data inconsistency.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ocfs2: fix buffer head management in ocfs2_read_blocks()</p> <p>In ocfs2_read_blocks(), caller should&#39;t assume that buffer head returned by &#39;sb_getblk()&#39; is exclusively owned and so &#39;put_bh()&#39; 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 &#39;sb_getblk()&#39; 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 &#39;validate()&#39; callback has detected some data inconsistency.</p> https://cve.radiocsirt.org/vuln/cve-2026-80881