<?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 07:08:09 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-45003</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-45003</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-45003</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0822 — 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://127.0.0.1:10001/vuln/certfr-2024-avi-0822</link>
      <description>certfr-2024-avi-0822</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0822</guid>
    </item>
    <item>
      <title>OESA-2024-2181 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2181</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
tcp: Use refcount_inc_not_zero() in tcp_twsk_unique().&#13;
&#13;
Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique()
with nice analysis.&#13;
&#13;
Since commit ec94c2696f0b (&amp;amp;quot;tcp/dccp: avoid one atomic operation for
timewait hashdance&amp;amp;quot;), inet_twsk_hashdance() sets TIME-WAIT socket&amp;amp;apos;s
sk_refcnt after putting it into ehash and releasing the bucket lock.&#13;
&#13;
Thus, there is a small race window where other threads could try to
reuse the port during connect() and call sock_hold() in tcp_twsk_unique()
for the TIME-WAIT socket with zero refcnt.&#13;
&#13;
If that happens, the refcnt taken by tcp_twsk_unique() is overwritten
and sock_put() will cause underflow, triggering a real use-after-free
somewhere else.&#13;
&#13;
To avoid the use-after-free, we need to use refcount_inc_not_zero() in
tcp_twsk_unique() and give up on reusing the port if it returns false.&#13;
&#13;
[0]:
refcount_t: addition on 0; use-after-free.
WARNING: CPU: 0 PID: 1039313 at lib/refcount.c:25 refcount_warn_saturate+0xe5/0x110
CPU: 0 PID: 1039313 Comm: trigger Not tainted 6.8.6-200.fc39.x86_64 #1
Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
RIP: 0010:refcount_warn_saturate+0xe5/0x110
Code: 42 8e ff 0f 0b c3 cc cc cc cc 80 3d aa 13 ea 01 00 0f 85 5e ff ff ff 48 c7 c7 f8 8e b7 82 c6 05 96 13 ea…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
tcp: Use refcount_inc_not_zero() in tcp_twsk_unique().&#13;
&#13;
Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique()
with nice analysis.&#13;
&#13;
Since commit ec94c2696f0b (&amp;amp;quot;tcp/dccp: avoid one atomic operation for
timewait hashdance&amp;amp;quot;), inet_twsk_hashdance() sets TIME-WAIT socket&amp;amp;apos;s
sk_refcnt after putting it into ehash and releasing the bucket lock.&#13;
&#13;
Thus, there is a small race window where other threads could try to
reuse the port during connect() and call sock_hold() in tcp_twsk_unique()
for the TIME-WAIT socket with zero refcnt.&#13;
&#13;
If that happens, the refcnt taken by tcp_twsk_unique() is overwritten
and sock_put() will cause underflow, triggering a real use-after-free
somewhere else.&#13;
&#13;
To avoid the use-after-free, we need to use refcount_inc_not_zero() in
tcp_twsk_unique() and give up on reusing the port if it returns false.&#13;
&#13;
[0]:
refcount_t: addition on 0; use-after-free.
WARNING: CPU: 0 PID: 1039313 at lib/refcount.c:25 refcount_warn_saturate+0xe5/0x110
CPU: 0 PID: 1039313 Comm: trigger Not tainted 6.8.6-200.fc39.x86_64 #1
Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
RIP: 0010:refcount_warn_saturate+0xe5/0x110
Code: 42 8e ff 0f 0b c3 cc cc cc cc 80 3d aa 13 ea 01 00 0f 85 5e ff ff ff 48 c7 c7 f8 8e b7 82 c6 05 96 13 ea…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2181</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-45003</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-45003</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfs: Don&amp;#39;t evict inode under the inode lru traversing context The inode reclaiming process(See function prune_icache_sb) collects all reclaimable inodes and mark them with I_FREEING flag at first, at that time, other processes will be stuck if they try getting these inodes (See function find_inode_fast), then the reclaiming process destroy the inodes by function dispose_list(). Some filesystems(eg. ext4 with ea_inode feature, ubifs with xattr) may do inode lookup in the inode evicting callback function, if the inode lookup is operated under the inode lru traversing context, deadlock problems may happen. Case 1: In function ext4_evict_inode(), the ea inode lookup could happen         if ea_inode feature is enabled, the lookup process will be stuck 	under the evicting context like this:  1. File A has inode i_reg and an ea inode i_ea  2. getfattr(A, xattr_buf) // i_ea is added into lru // lru-&amp;gt;i_ea  3. Then, following three processes running like this:     PA                              PB  echo 2 &amp;gt; /proc/sys/vm/drop_caches   shrink_slab    prune_dcache_sb    // i_reg is added into lru, lru-&amp;gt;i_ea-&amp;gt;i_reg    prune_icache_sb     list_lru_walk_one      inode_lru_isolate       i_ea-&amp;gt;i_state |= I_FREEING // set inode state      inode_lru_isolate       __iget(i_reg)       spin_unlock(&amp;amp;i_reg-&amp;gt;i_lock)       spin_unlock(lru_lock)                                      rm file A                                       i_reg…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfs: Don&amp;#39;t evict inode under the inode lru traversing context The inode reclaiming process(See function prune_icache_sb) collects all reclaimable inodes and mark them with I_FREEING flag at first, at that time, other processes will be stuck if they try getting these inodes (See function find_inode_fast), then the reclaiming process destroy the inodes by function dispose_list(). Some filesystems(eg. ext4 with ea_inode feature, ubifs with xattr) may do inode lookup in the inode evicting callback function, if the inode lookup is operated under the inode lru traversing context, deadlock problems may happen. Case 1: In function ext4_evict_inode(), the ea inode lookup could happen         if ea_inode feature is enabled, the lookup process will be stuck 	under the evicting context like this:  1. File A has inode i_reg and an ea inode i_ea  2. getfattr(A, xattr_buf) // i_ea is added into lru // lru-&amp;gt;i_ea  3. Then, following three processes running like this:     PA                              PB  echo 2 &amp;gt; /proc/sys/vm/drop_caches   shrink_slab    prune_dcache_sb    // i_reg is added into lru, lru-&amp;gt;i_ea-&amp;gt;i_reg    prune_icache_sb     list_lru_walk_one      inode_lru_isolate       i_ea-&amp;gt;i_state |= I_FREEING // set inode state      inode_lru_isolate       __iget(i_reg)       spin_unlock(&amp;amp;i_reg-&amp;gt;i_lock)       spin_unlock(lru_lock)                                      rm file A                                       i_reg…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-45003</guid>
    </item>
  </channel>
</rss>
