<?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 05:11:20 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-52635</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2023-52635</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-2023-52635</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>OESA-2024-1617 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1617</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
x86/kvm: Disable kvmclock on all CPUs on shutdown&#13;
&#13;
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&#13;
&#13;
Note, writing &amp;amp;apos;0&amp;amp;apos; to kvmclock MSR doesn&amp;amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix NULL ptr dereference on VSI filter sync&#13;
&#13;
Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;amp;apos;s causing a kernel oops.(CVE-2021-47184)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;
x86/kvm: Disable kvmclock on all CPUs on shutdown&#13;
&#13;
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.&#13;
&#13;
Note, writing &amp;amp;apos;0&amp;amp;apos; to kvmclock MSR doesn&amp;amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
i40e: Fix NULL ptr dereference on VSI filter sync&#13;
&#13;
Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;amp;apos;s causing a kernel oops.(CVE-2021-47184)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1617</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52635</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52635</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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: Synchronize devfreq_monitor_[start/stop] There is a chance if a frequent switch of the governor done in a loop result in timer list corruption where timer cancel being done from two place one from cancel_delayed_work_sync() and followed by expire_timers() can be seen from the traces[1]. while true do         echo &amp;#34;simple_ondemand&amp;#34; &amp;gt; /sys/class/devfreq/1d84000.ufshc/governor         echo &amp;#34;performance&amp;#34; &amp;gt; /sys/class/devfreq/1d84000.ufshc/governor done It looks to be issue with devfreq driver where device_monitor_[start/stop] need to synchronized so that delayed work should get corrupted while it is either being queued or running or being cancelled. Let&amp;#39;s use polling flag and devfreq lock to synchronize the queueing the timer instance twice and work data being corrupted. [1] ... .. &amp;lt;idle&amp;gt;-0    [003]   9436.209662:  timer_cancel   timer=0xffffff80444f0428 &amp;lt;idle&amp;gt;-0    [003]   9436.209664:  timer_expire_entry timer=0xffffff80444f0428  now=0x10022da1c function=__typeid__ZTSFvP10timer_listE_global_addr  baseclk=0x10022da1c &amp;lt;idle&amp;gt;-0    [003]   9436.209718:  timer_expire_exit timer=0xffffff80444f0428 kworker/u16:6-14217    [003]   9436.209863:  timer_start timer=0xffffff80444f0428 function=__typeid__ZTSFvP10timer_listE_global_addr  expires=0x10022da2b now=0x10022da1c  flags=182452227 vendor.xxxyyy.ha-1593    [004]   9436.209888:  timer_cancel timer=0xffffff80444f0428 vendor.xxxyyy.ha-1593    [004]   9436.…&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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: Synchronize devfreq_monitor_[start/stop] There is a chance if a frequent switch of the governor done in a loop result in timer list corruption where timer cancel being done from two place one from cancel_delayed_work_sync() and followed by expire_timers() can be seen from the traces[1]. while true do         echo &amp;#34;simple_ondemand&amp;#34; &amp;gt; /sys/class/devfreq/1d84000.ufshc/governor         echo &amp;#34;performance&amp;#34; &amp;gt; /sys/class/devfreq/1d84000.ufshc/governor done It looks to be issue with devfreq driver where device_monitor_[start/stop] need to synchronized so that delayed work should get corrupted while it is either being queued or running or being cancelled. Let&amp;#39;s use polling flag and devfreq lock to synchronize the queueing the timer instance twice and work data being corrupted. [1] ... .. &amp;lt;idle&amp;gt;-0    [003]   9436.209662:  timer_cancel   timer=0xffffff80444f0428 &amp;lt;idle&amp;gt;-0    [003]   9436.209664:  timer_expire_entry timer=0xffffff80444f0428  now=0x10022da1c function=__typeid__ZTSFvP10timer_listE_global_addr  baseclk=0x10022da1c &amp;lt;idle&amp;gt;-0    [003]   9436.209718:  timer_expire_exit timer=0xffffff80444f0428 kworker/u16:6-14217    [003]   9436.209863:  timer_start timer=0xffffff80444f0428 function=__typeid__ZTSFvP10timer_listE_global_addr  expires=0x10022da2b now=0x10022da1c  flags=182452227 vendor.xxxyyy.ha-1593    [004]   9436.209888:  timer_cancel timer=0xffffff80444f0428 vendor.xxxyyy.ha-1593    [004]   9436.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52635</guid>
    </item>
  </channel>
</rss>
