<?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 06:03:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56587</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56587</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-56587</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0088 — 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-2025-avi-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>OESA-2025-1286 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1286</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1286</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56587</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56587</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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: leds: class: Protect brightness_show() with led_cdev-&amp;gt;led_access mutex There is NULL pointer issue observed if from Process A where hid device being added which results in adding a led_cdev addition and later a another call to access of led_cdev attribute from Process B can result in NULL pointer issue. Use mutex led_cdev-&amp;gt;led_access to protect access to led-&amp;gt;cdev and its attribute inside brightness_show() and max_brightness_show() and also update the comment for mutex that it should be used to protect the led class device fields. 	Process A 				Process B  kthread+0x114  worker_thread+0x244  process_scheduled_works+0x248  uhid_device_add_worker+0x24  hid_add_device+0x120  device_add+0x268  bus_probe_device+0x94  device_initial_probe+0x14  __device_attach+0xfc  bus_for_each_drv+0x10c  __device_attach_driver+0x14c  driver_probe_device+0x3c  __driver_probe_device+0xa0  really_probe+0x190  hid_device_probe+0x130  ps_probe+0x990  ps_led_register+0x94  devm_led_classdev_register_ext+0x58  led_classdev_register_ext+0x1f8  device_create_with_groups+0x48  device_create_groups_vargs+0xc8  device_add+0x244  kobject_uevent+0x14  kobject_uevent_env[jt]+0x224  mutex_unlock[jt]+0xc4  __mutex_unlock_slowpath+0xd4  wake_up_q+0x70  try_to_wake_up[jt]+0x48c  preempt_schedule_common+0x28  __schedule+0x628  __switch_to+0x174 						el0t_64_sync+0x1a8/0x1ac 						el0t_64_sync_handler+0x68/0xbc 						el0_svc+0x38/0x68 						do_el0_…&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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: leds: class: Protect brightness_show() with led_cdev-&amp;gt;led_access mutex There is NULL pointer issue observed if from Process A where hid device being added which results in adding a led_cdev addition and later a another call to access of led_cdev attribute from Process B can result in NULL pointer issue. Use mutex led_cdev-&amp;gt;led_access to protect access to led-&amp;gt;cdev and its attribute inside brightness_show() and max_brightness_show() and also update the comment for mutex that it should be used to protect the led class device fields. 	Process A 				Process B  kthread+0x114  worker_thread+0x244  process_scheduled_works+0x248  uhid_device_add_worker+0x24  hid_add_device+0x120  device_add+0x268  bus_probe_device+0x94  device_initial_probe+0x14  __device_attach+0xfc  bus_for_each_drv+0x10c  __device_attach_driver+0x14c  driver_probe_device+0x3c  __driver_probe_device+0xa0  really_probe+0x190  hid_device_probe+0x130  ps_probe+0x990  ps_led_register+0x94  devm_led_classdev_register_ext+0x58  led_classdev_register_ext+0x1f8  device_create_with_groups+0x48  device_create_groups_vargs+0xc8  device_add+0x244  kobject_uevent+0x14  kobject_uevent_env[jt]+0x224  mutex_unlock[jt]+0xc4  __mutex_unlock_slowpath+0xd4  wake_up_q+0x70  try_to_wake_up[jt]+0x48c  preempt_schedule_common+0x28  __schedule+0x628  __switch_to+0x174 						el0t_64_sync+0x1a8/0x1ac 						el0t_64_sync_handler+0x68/0xbc 						el0_svc+0x38/0x68 						do_el0_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56587</guid>
    </item>
  </channel>
</rss>
