<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 04:31:01 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:11861 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:11861</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)
  * kernel: wifi: iwlwifi: limit printed string from FW file (CVE-2025-21905)
  * kernel: RDMA/mlx5: Fix page_size variable overflow (CVE-2025-22091)
  * kernel: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() (CVE-2025-22121)
  * kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113)
  * kernel: RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)
  * kernel: net_sched: hfsc: Fix a UAF vulnerability in class handling (CVE-2025-37797)
  * kernel: mm/huge_memory: fix dereferencing invalid pmd migration entry (CVE-2025-37958)
  * kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)
  * kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (CVE-2025-38110)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)
  * kernel: wifi: iwlwifi: limit printed string from FW file (CVE-2025-21905)
  * kernel: RDMA/mlx5: Fix page_size variable overflow (CVE-2025-22091)
  * kernel: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() (CVE-2025-22121)
  * kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113)
  * kernel: RDMA/core: Fix use-after-free when rename device name (CVE-2025-22085)
  * kernel: net_sched: hfsc: Fix a UAF vulnerability in class handling (CVE-2025-37797)
  * kernel: mm/huge_memory: fix dereferencing invalid pmd migration entry (CVE-2025-37958)
  * kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)
  * kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (CVE-2025-38110)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:11861</guid>
    </item>
    <item>
      <title>bdu:2026-02291</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02291</link>
      <description>bdu:2026-02291</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02291</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-22113</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-22113</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-22113</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0529 — 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://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</link>
      <description>certfr-2025-avi-0529</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</guid>
    </item>
    <item>
      <title>EUVD-2026-314187</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314187</link>
      <description>EUVD-2026-314187</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314187</guid>
    </item>
    <item>
      <title>fkie_cve-2025-22113</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22113</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: avoid journaling sb update on error if journal is destroying&lt;/p&gt;
&lt;p&gt;Presently we always BUG_ON if trying to start a transaction on a journal marked
with JBD2_UNMOUNT, since this should never happen. However, while ltp running
stress tests, it was observed that in case of some error handling paths, it is
possible for update_super_work to start a transaction after the journal is
destroyed eg:&lt;/p&gt;
&lt;p&gt;(umount)
ext4_kill_sb
  kill_block_super
    generic_shutdown_super
      sync_filesystem /* commits all txns */
      evict_inodes
        /* might start a new txn */
      ext4_put_super
	flush_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work) /* flush the workqueue */
        jbd2_journal_destroy
          journal_kill_thread
            journal-&amp;gt;j_flags |= JBD2_UNMOUNT;
          jbd2_journal_commit_transaction
            jbd2_journal_get_descriptor_buffer
              jbd2_journal_bmap
                ext4_journal_bmap
                  ext4_map_blocks
                    ...
                    ext4_inode_error
                      ext4_handle_error
                        schedule_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work)&lt;/p&gt;
&lt;p&gt;/* work queue kicks in */
                                               update_super_work
                                                 jbd2_journal_start
                                                   start_this_handle
                                                     BUG_…&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;ext4: avoid journaling sb update on error if journal is destroying&lt;/p&gt;
&lt;p&gt;Presently we always BUG_ON if trying to start a transaction on a journal marked
with JBD2_UNMOUNT, since this should never happen. However, while ltp running
stress tests, it was observed that in case of some error handling paths, it is
possible for update_super_work to start a transaction after the journal is
destroyed eg:&lt;/p&gt;
&lt;p&gt;(umount)
ext4_kill_sb
  kill_block_super
    generic_shutdown_super
      sync_filesystem /* commits all txns */
      evict_inodes
        /* might start a new txn */
      ext4_put_super
	flush_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work) /* flush the workqueue */
        jbd2_journal_destroy
          journal_kill_thread
            journal-&amp;gt;j_flags |= JBD2_UNMOUNT;
          jbd2_journal_commit_transaction
            jbd2_journal_get_descriptor_buffer
              jbd2_journal_bmap
                ext4_journal_bmap
                  ext4_map_blocks
                    ...
                    ext4_inode_error
                      ext4_handle_error
                        schedule_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work)&lt;/p&gt;
&lt;p&gt;/* work queue kicks in */
                                               update_super_work
                                                 jbd2_journal_start
                                                   start_this_handle
                                                     BUG_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-22113</guid>
    </item>
    <item>
      <title>GHSA-2gxm-8qch-c9vg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2gxm-8qch-c9vg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: avoid journaling sb update on error if journal is destroying&lt;/p&gt;
&lt;p&gt;Presently we always BUG_ON if trying to start a transaction on a journal marked
with JBD2_UNMOUNT, since this should never happen. However, while ltp running
stress tests, it was observed that in case of some error handling paths, it is
possible for update_super_work to start a transaction after the journal is
destroyed eg:&lt;/p&gt;
&lt;p&gt;(umount)
ext4_kill_sb
  kill_block_super
    generic_shutdown_super
      sync_filesystem /* commits all txns */
      evict_inodes
        /* might start a new txn */
      ext4_put_super
	flush_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work) /* flush the workqueue */
        jbd2_journal_destroy
          journal_kill_thread
            journal-&amp;gt;j_flags |= JBD2_UNMOUNT;
          jbd2_journal_commit_transaction
            jbd2_journal_get_descriptor_buffer
              jbd2_journal_bmap
                ext4_journal_bmap
                  ext4_map_blocks
                    ...
                    ext4_inode_error
                      ext4_handle_error
                        schedule_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work)&lt;/p&gt;
&lt;p&gt;/* work queue kicks in */
                                               update_super_work
                                                 jbd2_journal_start
                                                   start_this_handle
                                                     BUG_…&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;ext4: avoid journaling sb update on error if journal is destroying&lt;/p&gt;
&lt;p&gt;Presently we always BUG_ON if trying to start a transaction on a journal marked
with JBD2_UNMOUNT, since this should never happen. However, while ltp running
stress tests, it was observed that in case of some error handling paths, it is
possible for update_super_work to start a transaction after the journal is
destroyed eg:&lt;/p&gt;
&lt;p&gt;(umount)
ext4_kill_sb
  kill_block_super
    generic_shutdown_super
      sync_filesystem /* commits all txns */
      evict_inodes
        /* might start a new txn */
      ext4_put_super
	flush_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work) /* flush the workqueue */
        jbd2_journal_destroy
          journal_kill_thread
            journal-&amp;gt;j_flags |= JBD2_UNMOUNT;
          jbd2_journal_commit_transaction
            jbd2_journal_get_descriptor_buffer
              jbd2_journal_bmap
                ext4_journal_bmap
                  ext4_map_blocks
                    ...
                    ext4_inode_error
                      ext4_handle_error
                        schedule_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work)&lt;/p&gt;
&lt;p&gt;/* work queue kicks in */
                                               update_super_work
                                                 jbd2_journal_start
                                                   start_this_handle
                                                     BUG_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2gxm-8qch-c9vg</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-22113 — ext4: avoid journaling sb update on error if journal is destroying</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-22113</link>
      <description>msrc_CVE-2025-22113</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-22113</guid>
    </item>
    <item>
      <title>OESA-2025-1463 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1463</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/ASPM: Fix link state exit during switch upstream function removal&lt;/p&gt;
&lt;p&gt;Before 456d8aa37d0f (&amp;amp;quot;PCI/ASPM: Disable ASPM on MFD function removal to
avoid use-after-free&amp;amp;quot;), we would free the ASPM link only after the last
function on the bus pertaining to the given link was removed.&lt;/p&gt;
&lt;p&gt;That was too late. If function 0 is removed before sibling function,
link-&amp;amp;gt;downstream would point to free&amp;amp;apos;d memory after.&lt;/p&gt;
&lt;p&gt;After above change, we freed the ASPM parent link state upon any function
removal on the bus pertaining to a given link.&lt;/p&gt;
&lt;p&gt;That is too early. If the link is to a PCIe switch with MFD on the upstream
port, then removing functions other than 0 first would free a link which
still remains parent_link to the remaining downstream ports.&lt;/p&gt;
&lt;p&gt;The resulting GPFs are especially frequent during hot-unplug, because
pciehp removes devices on the link bus in reverse order.&lt;/p&gt;
&lt;p&gt;On that switch, function 0 is the virtual P2P bridge to the internal bus.
Free exactly when function 0 is removed -- before the parent link is
obsolete, but after all subordinate links are gone.&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2024-58093)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jfs: add check read-only before truncation in jfs_truncate_nolock()&lt;/p&gt;
&lt;p&gt;Added a check for &amp;amp;quot;read-only&amp;amp;quot; mode in the `jfs_truncate_nolock`
function to avoid errors…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/ASPM: Fix link state exit during switch upstream function removal&lt;/p&gt;
&lt;p&gt;Before 456d8aa37d0f (&amp;amp;quot;PCI/ASPM: Disable ASPM on MFD function removal to
avoid use-after-free&amp;amp;quot;), we would free the ASPM link only after the last
function on the bus pertaining to the given link was removed.&lt;/p&gt;
&lt;p&gt;That was too late. If function 0 is removed before sibling function,
link-&amp;amp;gt;downstream would point to free&amp;amp;apos;d memory after.&lt;/p&gt;
&lt;p&gt;After above change, we freed the ASPM parent link state upon any function
removal on the bus pertaining to a given link.&lt;/p&gt;
&lt;p&gt;That is too early. If the link is to a PCIe switch with MFD on the upstream
port, then removing functions other than 0 first would free a link which
still remains parent_link to the remaining downstream ports.&lt;/p&gt;
&lt;p&gt;The resulting GPFs are especially frequent during hot-unplug, because
pciehp removes devices on the link bus in reverse order.&lt;/p&gt;
&lt;p&gt;On that switch, function 0 is the virtual P2P bridge to the internal bus.
Free exactly when function 0 is removed -- before the parent link is
obsolete, but after all subordinate links are gone.&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2024-58093)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jfs: add check read-only before truncation in jfs_truncate_nolock()&lt;/p&gt;
&lt;p&gt;Added a check for &amp;amp;quot;read-only&amp;amp;quot; mode in the `jfs_truncate_nolock`
function to avoid errors…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1463</guid>
    </item>
    <item>
      <title>RHSA-2025:11810 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:11810</link>
      <description>&lt;p&gt;kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: perf/core: Bail out early if the request AUX area is out of bound kernel: rcu-tasks: Avoid pr_info() with spin lock in cblist_init_generic() kernel: drm/amd/display: Implement bounds check for stream encoder creation in DCN301 kernel: nbd: null check for nla_nest_start kernel: firmware: cs_dsp: Fix overflow checking of wmfw header kernel: powerpc/pseries: Whitelist dtl slub object for copying to userspace kernel: usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB kernel: parport: Proper fix for array out-of-bounds access kernel: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race kernel: ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up kernel: wifi: iwlwifi: limit printed string from FW file kernel: ibmvnic: Use kernel helpers for hex dumps kernel: ext4: avoid journaling sb update on error if journal is destroying kernel: udmabuf: fix a buf size overflow issue during udmabuf creation kernel: net/sched: fix use-after-free in taprio_dev_notifier kernel: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: perf/core: Bail out early if the request AUX area is out of bound kernel: rcu-tasks: Avoid pr_info() with spin lock in cblist_init_generic() kernel: drm/amd/display: Implement bounds check for stream encoder creation in DCN301 kernel: nbd: null check for nla_nest_start kernel: firmware: cs_dsp: Fix overflow checking of wmfw header kernel: powerpc/pseries: Whitelist dtl slub object for copying to userspace kernel: usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB kernel: parport: Proper fix for array out-of-bounds access kernel: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race kernel: ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up kernel: wifi: iwlwifi: limit printed string from FW file kernel: ibmvnic: Use kernel helpers for hex dumps kernel: ext4: avoid journaling sb update on error if journal is destroying kernel: udmabuf: fix a buf size overflow issue during udmabuf creation kernel: net/sched: fix use-after-free in taprio_dev_notifier kernel: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:11810</guid>
    </item>
    <item>
      <title>RHSA-2025:11861 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:11861</link>
      <description>&lt;p&gt;kernel: media: uvcvideo: Fix double free in error path kernel: wifi: iwlwifi: limit printed string from FW file kernel: RDMA/core: Fix use-after-free when rename device name kernel: RDMA/mlx5: Fix page_size variable overflow kernel: ext4: avoid journaling sb update on error if journal is destroying kernel: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() kernel: net_sched: hfsc: Fix a UAF vulnerability in class handling kernel: mm/huge_memory: fix dereferencing invalid pmd migration entry kernel: net: ch9200: fix uninitialised access during mii_nway_restart kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: media: uvcvideo: Fix double free in error path kernel: wifi: iwlwifi: limit printed string from FW file kernel: RDMA/core: Fix use-after-free when rename device name kernel: RDMA/mlx5: Fix page_size variable overflow kernel: ext4: avoid journaling sb update on error if journal is destroying kernel: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() kernel: net_sched: hfsc: Fix a UAF vulnerability in class handling kernel: mm/huge_memory: fix dereferencing invalid pmd migration entry kernel: net: ch9200: fix uninitialised access during mii_nway_restart kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:11861</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02249-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02249-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://cve.radiocsirt.org/vuln/suse-su-2025:02249-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-22113</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22113</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 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: avoid journaling sb update on error if journal is destroying Presently we always BUG_ON if trying to start a transaction on a journal marked with JBD2_UNMOUNT, since this should never happen. However, while ltp running stress tests, it was observed that in case of some error handling paths, it is possible for update_super_work to start a transaction after the journal is destroyed eg: (umount) ext4_kill_sb   kill_block_super     generic_shutdown_super       sync_filesystem /* commits all txns */       evict_inodes         /* might start a new txn */       ext4_put_super 	flush_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work) /* flush the workqueue */         jbd2_journal_destroy           journal_kill_thread             journal-&amp;gt;j_flags |= JBD2_UNMOUNT;           jbd2_journal_commit_transaction             jbd2_journal_get_descriptor_buffer               jbd2_journal_bmap                 ext4_journal_bmap                   ext4_map_blocks                     ...                     ext4_inode_error                       ext4_handle_error                         schedule_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work)                                                /* work queue kicks in */                                                update_super_work                                                  jbd2_journal_start                                                    start_this_handle BUG_ON(journal-&amp;gt;j_flags &amp;amp;…&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 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: avoid journaling sb update on error if journal is destroying Presently we always BUG_ON if trying to start a transaction on a journal marked with JBD2_UNMOUNT, since this should never happen. However, while ltp running stress tests, it was observed that in case of some error handling paths, it is possible for update_super_work to start a transaction after the journal is destroyed eg: (umount) ext4_kill_sb   kill_block_super     generic_shutdown_super       sync_filesystem /* commits all txns */       evict_inodes         /* might start a new txn */       ext4_put_super 	flush_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work) /* flush the workqueue */         jbd2_journal_destroy           journal_kill_thread             journal-&amp;gt;j_flags |= JBD2_UNMOUNT;           jbd2_journal_commit_transaction             jbd2_journal_get_descriptor_buffer               jbd2_journal_bmap                 ext4_journal_bmap                   ext4_map_blocks                     ...                     ext4_inode_error                       ext4_handle_error                         schedule_work(&amp;amp;sbi-&amp;gt;s_sb_upd_work)                                                /* work queue kicks in */                                                update_super_work                                                  jbd2_journal_start                                                    start_this_handle BUG_ON(journal-&amp;gt;j_flags &amp;amp;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22113</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0844 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</guid>
    </item>
  </channel>
</rss>
