https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 12:18:36 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-80881 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-80881 https://cve.radiocsirt.org/vuln/euvd-2026-363920 EUVD-2026-363920 https://cve.radiocsirt.org/vuln/euvd-2026-363920 https://cve.radiocsirt.org/vuln/fkie_cve-2026-80881 <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>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/fkie_cve-2026-80881 https://cve.radiocsirt.org/vuln/ghsa-5x8p-2x56-54gv <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>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/ghsa-5x8p-2x56-54gv https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80881 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 242 more</p> <p>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&#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> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 242 more</p> <p>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&#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/ubuntu-cve-2026-80881 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211