<?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>Fri, 20 Nov 2026 23:30:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38727</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38727</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-38727</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>OESA-2025-2802 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2802</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;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&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;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2802</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38727</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38727</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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket&amp;#39;s read memory allocation constraints. Firstly, it has:   rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) to check if the just increased rmem value fits into the socket&amp;#39;s receive buffer. If not, it proceeds and tries to wait for the memory under:   rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as:   rcu: INFO: rcu_sched self-detected stall on CPU   rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212   (t=26000 jiffies g=230833 q=259957)   NMI backtrace for cpu 0   CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014   Call Trace:   &amp;lt;IRQ&amp;gt;   dump_stack lib/dump_stack.c:120   nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105   nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62   rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335   rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590   update_process_times kernel/time/timer.c:1953   tick_sched_handle kernel/time/tick-sched.c:227   tick_sched_timer kernel/time/tick-sched.c:1399   __hrtimer_run_q…&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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket&amp;#39;s read memory allocation constraints. Firstly, it has:   rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) to check if the just increased rmem value fits into the socket&amp;#39;s receive buffer. If not, it proceeds and tries to wait for the memory under:   rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as:   rcu: INFO: rcu_sched self-detected stall on CPU   rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212   (t=26000 jiffies g=230833 q=259957)   NMI backtrace for cpu 0   CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014   Call Trace:   &amp;lt;IRQ&amp;gt;   dump_stack lib/dump_stack.c:120   nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105   nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62   rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335   rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590   update_process_times kernel/time/timer.c:1953   tick_sched_handle kernel/time/tick-sched.c:227   tick_sched_timer kernel/time/tick-sched.c:1399   __hrtimer_run_q…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38727</guid>
    </item>
  </channel>
</rss>
