<?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:36:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38222</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38222</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-2025-38222</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>OESA-2025-1959 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1959</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;xfrm: state: fix out-of-bounds read during lookup&lt;/p&gt;
&lt;p&gt;lookup and resize can run in parallel.&lt;/p&gt;
&lt;p&gt;The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.&lt;/p&gt;
&lt;p&gt;rehash does:
  rcu_assign_pointer(net-&amp;amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;amp;gt;xfrm.state_hmask = nhashmask;&lt;/p&gt;
&lt;p&gt;While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;amp;gt;xfrm.state_bydst + h, bydst) {&lt;/p&gt;
&lt;p&gt;This is only safe in case the update to state_bydst is larger than
net-&amp;amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).&lt;/p&gt;
&lt;p&gt;Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.&lt;/p&gt;
&lt;p&gt;The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.&lt;/p&gt;
&lt;p&gt;xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eth: bnxt: always recalculate features after XDP clearing, fix n…&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;xfrm: state: fix out-of-bounds read during lookup&lt;/p&gt;
&lt;p&gt;lookup and resize can run in parallel.&lt;/p&gt;
&lt;p&gt;The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.&lt;/p&gt;
&lt;p&gt;rehash does:
  rcu_assign_pointer(net-&amp;amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;amp;gt;xfrm.state_hmask = nhashmask;&lt;/p&gt;
&lt;p&gt;While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;amp;gt;xfrm.state_bydst + h, bydst) {&lt;/p&gt;
&lt;p&gt;This is only safe in case the update to state_bydst is larger than
net-&amp;amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).&lt;/p&gt;
&lt;p&gt;Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.&lt;/p&gt;
&lt;p&gt;The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.&lt;/p&gt;
&lt;p&gt;xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eth: bnxt: always recalculate features after XDP clearing, fix n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1959</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38222</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38222</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 214 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below.         fd = open(&amp;#34;file1&amp;#34;, O_RDWR | O_CREAT | O_TRUNC, 0666);         ftruncate(fd, 30);         pwrite(fd, &amp;#34;a&amp;#34;, 1, (1UL &amp;lt;&amp;lt; 40) + 5UL); That happens because write_begin will succeed as when ext4_generic_write_inline_data calls ext4_prepare_inline_data, pos + len will be truncated, leading to ext4_prepare_inline_data parameter to be 6 instead of 0x10000000006. Then, later when write_end is called, we hit:         BUG_ON(pos + len &amp;gt; EXT4_I(inode)-&amp;gt;i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [   44.545164] ------------[ cut here ]------------ [   44.545530] kernel BUG at fs/ext4/inline.c:240! [   44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [   44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [   44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [   44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [   44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b &amp;lt;0f&amp;gt; 0b 0f 1f 44 00 00 55…&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 214 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below.         fd = open(&amp;#34;file1&amp;#34;, O_RDWR | O_CREAT | O_TRUNC, 0666);         ftruncate(fd, 30);         pwrite(fd, &amp;#34;a&amp;#34;, 1, (1UL &amp;lt;&amp;lt; 40) + 5UL); That happens because write_begin will succeed as when ext4_generic_write_inline_data calls ext4_prepare_inline_data, pos + len will be truncated, leading to ext4_prepare_inline_data parameter to be 6 instead of 0x10000000006. Then, later when write_end is called, we hit:         BUG_ON(pos + len &amp;gt; EXT4_I(inode)-&amp;gt;i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [   44.545164] ------------[ cut here ]------------ [   44.545530] kernel BUG at fs/ext4/inline.c:240! [   44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [   44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [   44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [   44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [   44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b &amp;lt;0f&amp;gt; 0b 0f 1f 44 00 00 55…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38222</guid>
    </item>
  </channel>
</rss>
