<?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 02:19:18 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-40980</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-40980</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-40980</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — 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-2024-avi-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>OESA-2024-1941 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1941</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1941</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-40980</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40980</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 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drop_monitor: replace spin_lock by raw_spin_lock trace_drop_common() is called with preemption disabled, and it acquires a spin_lock. This is problematic for RT kernels because spin_locks are sleeping locks in this configuration, which causes the following splat: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 449, name: rcuc/47 preempt_count: 1, expected: 0 RCU nest depth: 2, expected: 2 5 locks held by rcuc/47/449:  #0: ff1100086ec30a60 ((softirq_ctrl.lock)){+.+.}-{2:2}, at: __local_bh_disable_ip+0x105/0x210  #1: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: rt_spin_lock+0xbf/0x130  #2: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: __local_bh_disable_ip+0x11c/0x210  #3: ffffffffb394a160 (rcu_callback){....}-{0:0}, at: rcu_do_batch+0x360/0xc70  #4: ff1100086ee07520 (&amp;amp;data-&amp;gt;lock){+.+.}-{2:2}, at: trace_drop_common.constprop.0+0xb5/0x290 irq event stamp: 139909 hardirqs last  enabled at (139908): [&amp;lt;ffffffffb1df2b33&amp;gt;] _raw_spin_unlock_irqrestore+0x63/0x80 hardirqs last disabled at (139909): [&amp;lt;ffffffffb19bd03d&amp;gt;] trace_drop_common.constprop.0+0x26d/0x290 softirqs last  enabled at (139892): [&amp;lt;ffffffffb07a1083&amp;gt;] __local_bh_enable_ip+0x103/0x170 softirqs last disabled at (139898): [&amp;lt;ffffffffb0909b33&amp;gt;] rcu_cpu_kthread+0x93/0x1f0 Preemption disabled at: [&amp;lt;ffffffffb1de786b&amp;gt;] rt_mutex_slowunlock+0xab/0x2e0 CPU: 47 PID:…&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 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drop_monitor: replace spin_lock by raw_spin_lock trace_drop_common() is called with preemption disabled, and it acquires a spin_lock. This is problematic for RT kernels because spin_locks are sleeping locks in this configuration, which causes the following splat: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 449, name: rcuc/47 preempt_count: 1, expected: 0 RCU nest depth: 2, expected: 2 5 locks held by rcuc/47/449:  #0: ff1100086ec30a60 ((softirq_ctrl.lock)){+.+.}-{2:2}, at: __local_bh_disable_ip+0x105/0x210  #1: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: rt_spin_lock+0xbf/0x130  #2: ffffffffb394a280 (rcu_read_lock){....}-{1:2}, at: __local_bh_disable_ip+0x11c/0x210  #3: ffffffffb394a160 (rcu_callback){....}-{0:0}, at: rcu_do_batch+0x360/0xc70  #4: ff1100086ee07520 (&amp;amp;data-&amp;gt;lock){+.+.}-{2:2}, at: trace_drop_common.constprop.0+0xb5/0x290 irq event stamp: 139909 hardirqs last  enabled at (139908): [&amp;lt;ffffffffb1df2b33&amp;gt;] _raw_spin_unlock_irqrestore+0x63/0x80 hardirqs last disabled at (139909): [&amp;lt;ffffffffb19bd03d&amp;gt;] trace_drop_common.constprop.0+0x26d/0x290 softirqs last  enabled at (139892): [&amp;lt;ffffffffb07a1083&amp;gt;] __local_bh_enable_ip+0x103/0x170 softirqs last disabled at (139898): [&amp;lt;ffffffffb0909b33&amp;gt;] rcu_cpu_kthread+0x93/0x1f0 Preemption disabled at: [&amp;lt;ffffffffb1de786b&amp;gt;] rt_mutex_slowunlock+0xab/0x2e0 CPU: 47 PID:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40980</guid>
    </item>
  </channel>
</rss>
