<?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://127.0.0.1:10001</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, 21 Nov 2026 00:48:29 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-42297</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-42297</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://127.0.0.1:10001/vuln/bell-cve-2024-42297</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0872 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0872</link>
      <description>certfr-2024-avi-0872</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0872</guid>
    </item>
    <item>
      <title>OESA-2024-2077 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2077</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: get rid of warning on transaction commit when using flushoncommit&#13;
&#13;
When using the flushoncommit mount option, during almost every transaction
commit we trigger a warning from __writeback_inodes_sb_nr():&#13;
&#13;
  $ cat fs/fs-writeback.c:
  (...)
  static void __writeback_inodes_sb_nr(struct super_block *sb, ...
  {
        (...)
        WARN_ON(!rwsem_is_locked(&amp;amp;amp;sb-&amp;amp;gt;s_umount));
        (...)
  }
  (...)&#13;
&#13;
The trace produced in dmesg looks like the following:&#13;
&#13;
  [947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3
  [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif
  [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186
  [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3
  [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...)
  [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246
  [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000
  [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50
  [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000
  [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488
  [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ff…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: get rid of warning on transaction commit when using flushoncommit&#13;
&#13;
When using the flushoncommit mount option, during almost every transaction
commit we trigger a warning from __writeback_inodes_sb_nr():&#13;
&#13;
  $ cat fs/fs-writeback.c:
  (...)
  static void __writeback_inodes_sb_nr(struct super_block *sb, ...
  {
        (...)
        WARN_ON(!rwsem_is_locked(&amp;amp;amp;sb-&amp;amp;gt;s_umount));
        (...)
  }
  (...)&#13;
&#13;
The trace produced in dmesg looks like the following:&#13;
&#13;
  [947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3
  [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif
  [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186
  [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3
  [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...)
  [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246
  [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000
  [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50
  [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000
  [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488
  [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2077</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-42297</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42297</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 187 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don&amp;#39;t dirty inode for readonly filesystem syzbot reports f2fs bug as below: kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace:  evict+0x2a4/0x620 fs/inode.c:664  dispose_list fs/inode.c:697 [inline]  evict_inodes+0x5f8/0x690 fs/inode.c:747  generic_shutdown_super+0x9d/0x2c0 fs/super.c:675  kill_block_super+0x44/0x90 fs/super.c:1667  kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894  deactivate_locked_super+0xc1/0x130 fs/super.c:484  cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256  task_work_run+0x24a/0x300 kernel/task_work.c:180  ptrace_notify+0x2cd/0x380 kernel/signal.c:2399  ptrace_report_syscall include/linux/ptrace.h:411 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]  syscall_exit_work kernel/entry/common.c:251 [inline]  syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]  syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296  do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88  entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open  - f2fs_lookup   - __f2fs_find_entry    - f2fs_i_depth_write     - f2fs_mark_inode_dirty_sync      - f2fs_dirty_inode       - set_inode_flag(inode, FI_DIRTY_INODE) - umount  - kill_f2fs_super   - kill_block_super    - generic_shutdown_super     - sync_filesystem     : sb is…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 187 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don&amp;#39;t dirty inode for readonly filesystem syzbot reports f2fs bug as below: kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace:  evict+0x2a4/0x620 fs/inode.c:664  dispose_list fs/inode.c:697 [inline]  evict_inodes+0x5f8/0x690 fs/inode.c:747  generic_shutdown_super+0x9d/0x2c0 fs/super.c:675  kill_block_super+0x44/0x90 fs/super.c:1667  kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894  deactivate_locked_super+0xc1/0x130 fs/super.c:484  cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256  task_work_run+0x24a/0x300 kernel/task_work.c:180  ptrace_notify+0x2cd/0x380 kernel/signal.c:2399  ptrace_report_syscall include/linux/ptrace.h:411 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]  syscall_exit_work kernel/entry/common.c:251 [inline]  syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]  syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296  do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88  entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open  - f2fs_lookup   - __f2fs_find_entry    - f2fs_i_depth_write     - f2fs_mark_inode_dirty_sync      - f2fs_dirty_inode       - set_inode_flag(inode, FI_DIRTY_INODE) - umount  - kill_f2fs_super   - kill_block_super    - generic_shutdown_super     - sync_filesystem     : sb is…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-42297</guid>
    </item>
  </channel>
</rss>
