<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 01:49:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-16239</title>
      <link>https://db.gcve.eu/vuln/bdu:2025-16239</link>
      <description>bdu:2025-16239</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2025-16239</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://db.gcve.eu/vuln/certfr-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53526</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2023-53526</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jbd2: check &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before removing it from checkpoint&lt;/p&gt;
&lt;p&gt;Following process will corrupt ext4 image:
Step 1:
jbd2_journal_commit_transaction
 __jbd2_journal_insert_checkpoint(jh, commit_transaction)
 // Put jh into trans1-&amp;gt;t_checkpoint_list
 journal-&amp;gt;j_checkpoint_transactions = commit_transaction
 // Put trans1 into journal-&amp;gt;j_checkpoint_transactions&lt;/p&gt;
&lt;p&gt;Step 2:
do_get_write_access
 test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty
 __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2&lt;/p&gt;
&lt;p&gt;Step 3:
drop_cache
 journal_shrink_one_cp_list
  jbd2_journal_try_remove_checkpoint
   if (!trylock_buffer(bh))  // lock bh, true
   if (buffer_dirty(bh))     // buffer is not dirty
   __jbd2_journal_remove_checkpoint(jh)
   // remove jh from trans1-&amp;gt;t_checkpoint_list&lt;/p&gt;
&lt;p&gt;Step 4:
jbd2_log_do_checkpoint
 trans1 = journal-&amp;gt;j_checkpoint_transactions
 // jh is not in trans1-&amp;gt;t_checkpoint_list
 jbd2_cleanup_journal_tail(journal)  // trans1 is done&lt;/p&gt;
&lt;p&gt;Step 5: Power cut, trans2 is not committed, jh is lost in next mounting.&lt;/p&gt;
&lt;p&gt;Fix it by checking &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before remove it from checkpoint.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jbd2: check &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before removing it from checkpoint&lt;/p&gt;
&lt;p&gt;Following process will corrupt ext4 image:
Step 1:
jbd2_journal_commit_transaction
 __jbd2_journal_insert_checkpoint(jh, commit_transaction)
 // Put jh into trans1-&amp;gt;t_checkpoint_list
 journal-&amp;gt;j_checkpoint_transactions = commit_transaction
 // Put trans1 into journal-&amp;gt;j_checkpoint_transactions&lt;/p&gt;
&lt;p&gt;Step 2:
do_get_write_access
 test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty
 __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2&lt;/p&gt;
&lt;p&gt;Step 3:
drop_cache
 journal_shrink_one_cp_list
  jbd2_journal_try_remove_checkpoint
   if (!trylock_buffer(bh))  // lock bh, true
   if (buffer_dirty(bh))     // buffer is not dirty
   __jbd2_journal_remove_checkpoint(jh)
   // remove jh from trans1-&amp;gt;t_checkpoint_list&lt;/p&gt;
&lt;p&gt;Step 4:
jbd2_log_do_checkpoint
 trans1 = journal-&amp;gt;j_checkpoint_transactions
 // jh is not in trans1-&amp;gt;t_checkpoint_list
 jbd2_cleanup_journal_tail(journal)  // trans1 is done&lt;/p&gt;
&lt;p&gt;Step 5: Power cut, trans2 is not committed, jh is lost in next mounting.&lt;/p&gt;
&lt;p&gt;Fix it by checking &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before remove it from checkpoint.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2023-53526</guid>
    </item>
    <item>
      <title>GHSA-rhfj-r57g-8474</title>
      <link>https://db.gcve.eu/vuln/ghsa-rhfj-r57g-8474</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jbd2: check &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before removing it from checkpoint&lt;/p&gt;
&lt;p&gt;Following process will corrupt ext4 image:
Step 1:
jbd2_journal_commit_transaction
 __jbd2_journal_insert_checkpoint(jh, commit_transaction)
 // Put jh into trans1-&amp;gt;t_checkpoint_list
 journal-&amp;gt;j_checkpoint_transactions = commit_transaction
 // Put trans1 into journal-&amp;gt;j_checkpoint_transactions&lt;/p&gt;
&lt;p&gt;Step 2:
do_get_write_access
 test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty
 __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2&lt;/p&gt;
&lt;p&gt;Step 3:
drop_cache
 journal_shrink_one_cp_list
  jbd2_journal_try_remove_checkpoint
   if (!trylock_buffer(bh))  // lock bh, true
   if (buffer_dirty(bh))     // buffer is not dirty
   __jbd2_journal_remove_checkpoint(jh)
   // remove jh from trans1-&amp;gt;t_checkpoint_list&lt;/p&gt;
&lt;p&gt;Step 4:
jbd2_log_do_checkpoint
 trans1 = journal-&amp;gt;j_checkpoint_transactions
 // jh is not in trans1-&amp;gt;t_checkpoint_list
 jbd2_cleanup_journal_tail(journal)  // trans1 is done&lt;/p&gt;
&lt;p&gt;Step 5: Power cut, trans2 is not committed, jh is lost in next mounting.&lt;/p&gt;
&lt;p&gt;Fix it by checking &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before remove it from checkpoint.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jbd2: check &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before removing it from checkpoint&lt;/p&gt;
&lt;p&gt;Following process will corrupt ext4 image:
Step 1:
jbd2_journal_commit_transaction
 __jbd2_journal_insert_checkpoint(jh, commit_transaction)
 // Put jh into trans1-&amp;gt;t_checkpoint_list
 journal-&amp;gt;j_checkpoint_transactions = commit_transaction
 // Put trans1 into journal-&amp;gt;j_checkpoint_transactions&lt;/p&gt;
&lt;p&gt;Step 2:
do_get_write_access
 test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty
 __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2&lt;/p&gt;
&lt;p&gt;Step 3:
drop_cache
 journal_shrink_one_cp_list
  jbd2_journal_try_remove_checkpoint
   if (!trylock_buffer(bh))  // lock bh, true
   if (buffer_dirty(bh))     // buffer is not dirty
   __jbd2_journal_remove_checkpoint(jh)
   // remove jh from trans1-&amp;gt;t_checkpoint_list&lt;/p&gt;
&lt;p&gt;Step 4:
jbd2_log_do_checkpoint
 trans1 = journal-&amp;gt;j_checkpoint_transactions
 // jh is not in trans1-&amp;gt;t_checkpoint_list
 jbd2_cleanup_journal_tail(journal)  // trans1 is done&lt;/p&gt;
&lt;p&gt;Step 5: Power cut, trans2 is not committed, jh is lost in next mounting.&lt;/p&gt;
&lt;p&gt;Fix it by checking &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before remove it from checkpoint.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-rhfj-r57g-8474</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2025:03600-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/suse-su-2025:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53526</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2023-53526</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 115 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jbd2: check &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction  __jbd2_journal_insert_checkpoint(jh, commit_transaction)  // Put jh into trans1-&amp;gt;t_checkpoint_list  journal-&amp;gt;j_checkpoint_transactions = commit_transaction  // Put trans1 into journal-&amp;gt;j_checkpoint_transactions Step 2: do_get_write_access  test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty  __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache  journal_shrink_one_cp_list   jbd2_journal_try_remove_checkpoint    if (!trylock_buffer(bh))  // lock bh, true    if (buffer_dirty(bh))     // buffer is not dirty    __jbd2_journal_remove_checkpoint(jh)    // remove jh from trans1-&amp;gt;t_checkpoint_list Step 4: jbd2_log_do_checkpoint  trans1 = journal-&amp;gt;j_checkpoint_transactions  // jh is not in trans1-&amp;gt;t_checkpoint_list  jbd2_cleanup_journal_tail(journal)  // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before remove it from checkpoint.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 115 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jbd2: check &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction  __jbd2_journal_insert_checkpoint(jh, commit_transaction)  // Put jh into trans1-&amp;gt;t_checkpoint_list  journal-&amp;gt;j_checkpoint_transactions = commit_transaction  // Put trans1 into journal-&amp;gt;j_checkpoint_transactions Step 2: do_get_write_access  test_clear_buffer_dirty(bh) // clear buffer dirty，set jbd dirty  __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache  journal_shrink_one_cp_list   jbd2_journal_try_remove_checkpoint    if (!trylock_buffer(bh))  // lock bh, true    if (buffer_dirty(bh))     // buffer is not dirty    __jbd2_journal_remove_checkpoint(jh)    // remove jh from trans1-&amp;gt;t_checkpoint_list Step 4: jbd2_log_do_checkpoint  trans1 = journal-&amp;gt;j_checkpoint_transactions  // jh is not in trans1-&amp;gt;t_checkpoint_list  jbd2_cleanup_journal_tail(journal)  // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking &amp;#39;jh-&amp;gt;b_transaction&amp;#39; before remove it from checkpoint.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2023-53526</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
