<?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>Thu, 19 Nov 2026 17:53:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-50140</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-50140</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-50140</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>OESA-2025-1594 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1594</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;net: test for not too small csum_start in virtio_net_hdr_to_skb()&lt;/p&gt;
&lt;p&gt;syzbot was able to trigger this warning [1], after injecting a
malicious packet through af_packet, setting skb-&amp;amp;gt;csum_start and thus
the transport header to an incorrect value.&lt;/p&gt;
&lt;p&gt;We can at least make sure the transport header is after
the end of the network header (with a estimated minimal size).&lt;/p&gt;
&lt;p&gt;[1]
[   67.873027] skb len=4096 headroom=16 headlen=14 tailroom=0
mac=(-1,-1) mac_len=0 net=(16,-6) trans=10
shinfo(txflags=0 nr_frags=1 gso(size=0 type=0 segs=0))
csum(0xa start=10 offset=0 ip_summed=3 complete_sw=0 valid=0 level=0)
hash(0x0 sw=0 l4=0) proto=0x0800 pkttype=0 iif=0
priority=0x0 mark=0x0 alloc_cpu=10 vlan_all=0x0
encapsulation=0 inner(proto=0x0000, mac=0, net=0, trans=0)
[   67.877172] dev name=veth0_vlan feat=0x000061164fdd09e9
[   67.877764] sk family=17 type=3 proto=0
[   67.878279] skb linear:   00000000: 00 00 10 00 00 00 00 00 0f 00 00 00 08 00
[   67.879128] skb frag:     00000000: 0e 00 07 00 00 00 28 00 08 80 1c 00 04 00 00 02
[   67.879877] skb frag:     00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[   67.880647] skb frag:     00000020: 00 00 02 00 00 00 08 00 1b 00 00 00 00 00 00 00
[   67.881156] skb frag:     00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[   67.881753] skb frag:     00000040: 00 00 00 00 00 00 00 00 00 00…&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;net: test for not too small csum_start in virtio_net_hdr_to_skb()&lt;/p&gt;
&lt;p&gt;syzbot was able to trigger this warning [1], after injecting a
malicious packet through af_packet, setting skb-&amp;amp;gt;csum_start and thus
the transport header to an incorrect value.&lt;/p&gt;
&lt;p&gt;We can at least make sure the transport header is after
the end of the network header (with a estimated minimal size).&lt;/p&gt;
&lt;p&gt;[1]
[   67.873027] skb len=4096 headroom=16 headlen=14 tailroom=0
mac=(-1,-1) mac_len=0 net=(16,-6) trans=10
shinfo(txflags=0 nr_frags=1 gso(size=0 type=0 segs=0))
csum(0xa start=10 offset=0 ip_summed=3 complete_sw=0 valid=0 level=0)
hash(0x0 sw=0 l4=0) proto=0x0800 pkttype=0 iif=0
priority=0x0 mark=0x0 alloc_cpu=10 vlan_all=0x0
encapsulation=0 inner(proto=0x0000, mac=0, net=0, trans=0)
[   67.877172] dev name=veth0_vlan feat=0x000061164fdd09e9
[   67.877764] sk family=17 type=3 proto=0
[   67.878279] skb linear:   00000000: 00 00 10 00 00 00 00 00 0f 00 00 00 08 00
[   67.879128] skb frag:     00000000: 0e 00 07 00 00 00 28 00 08 80 1c 00 04 00 00 02
[   67.879877] skb frag:     00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[   67.880647] skb frag:     00000020: 00 00 02 00 00 00 08 00 1b 00 00 00 00 00 00 00
[   67.881156] skb frag:     00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[   67.881753] skb frag:     00000040: 00 00 00 00 00 00 00 00 00 00…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1594</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50140</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50140</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 101 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/core: Disable page allocation in task_tick_mm_cid() With KASAN and PREEMPT_RT enabled, calling task_work_add() in task_tick_mm_cid() may cause the following splat. [   63.696416] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [   63.696416] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 610, name: modprobe [   63.696416] preempt_count: 10001, expected: 0 [   63.696416] RCU nest depth: 1, expected: 1 This problem is caused by the following call trace.   sched_tick() [ acquire rq-&amp;gt;__lock ]    -&amp;gt; task_tick_mm_cid()     -&amp;gt; task_work_add()      -&amp;gt; __kasan_record_aux_stack()       -&amp;gt; kasan_save_stack()        -&amp;gt; stack_depot_save_flags()         -&amp;gt; alloc_pages_mpol_noprof()          -&amp;gt; __alloc_pages_noprof() 	  -&amp;gt; get_page_from_freelist() 	   -&amp;gt; rmqueue() 	    -&amp;gt; rmqueue_pcplist() 	     -&amp;gt; __rmqueue_pcplist() 	      -&amp;gt; rmqueue_bulk() 	       -&amp;gt; rt_spin_lock() The rq lock is a raw_spinlock_t. We can&amp;#39;t sleep while holding it. IOW, we can&amp;#39;t call alloc_pages() in stack_depot_save_flags(). The task_tick_mm_cid() function with its task_work_add() call was introduced by commit 223baf9d17f2 (&amp;#34;sched: Fix performance regression introduced by mm_cid&amp;#34;) in v6.4 kernel. Fortunately, there is a kasan_record_aux_stack_noalloc() variant that calls stack_depot_save_flags() while not allowing it to allocate new pages.  To allow task_tick_mm_cid() to use task_work without page alloc…&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 101 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/core: Disable page allocation in task_tick_mm_cid() With KASAN and PREEMPT_RT enabled, calling task_work_add() in task_tick_mm_cid() may cause the following splat. [   63.696416] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [   63.696416] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 610, name: modprobe [   63.696416] preempt_count: 10001, expected: 0 [   63.696416] RCU nest depth: 1, expected: 1 This problem is caused by the following call trace.   sched_tick() [ acquire rq-&amp;gt;__lock ]    -&amp;gt; task_tick_mm_cid()     -&amp;gt; task_work_add()      -&amp;gt; __kasan_record_aux_stack()       -&amp;gt; kasan_save_stack()        -&amp;gt; stack_depot_save_flags()         -&amp;gt; alloc_pages_mpol_noprof()          -&amp;gt; __alloc_pages_noprof() 	  -&amp;gt; get_page_from_freelist() 	   -&amp;gt; rmqueue() 	    -&amp;gt; rmqueue_pcplist() 	     -&amp;gt; __rmqueue_pcplist() 	      -&amp;gt; rmqueue_bulk() 	       -&amp;gt; rt_spin_lock() The rq lock is a raw_spinlock_t. We can&amp;#39;t sleep while holding it. IOW, we can&amp;#39;t call alloc_pages() in stack_depot_save_flags(). The task_tick_mm_cid() function with its task_work_add() call was introduced by commit 223baf9d17f2 (&amp;#34;sched: Fix performance regression introduced by mm_cid&amp;#34;) in v6.4 kernel. Fortunately, there is a kasan_record_aux_stack_noalloc() variant that calls stack_depot_save_flags() while not allowing it to allocate new pages.  To allow task_tick_mm_cid() to use task_work without page alloc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50140</guid>
    </item>
  </channel>
</rss>
