<?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:19:18 +0000</lastBuildDate>
    <item>
      <title>OESA-2026-1231 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-1231</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()&lt;/p&gt;
&lt;p&gt;When executing SMP task failed, the smp_execute_task_sg() calls del_timer()
to delete &amp;amp;quot;slow_task-&amp;amp;gt;timer&amp;amp;quot;. However, if the timer handler
sas_task_internal_timedout() is running, the del_timer() in
smp_execute_task_sg() will not stop it and a UAF will happen. The process
is shown below:&lt;/p&gt;
&lt;p&gt;(thread 1)               |        (thread 2)
smp_execute_task_sg()          | sas_task_internal_timedout()
 ...                           |
 del_timer()                   |
 ...                           |  ...
 sas_free_task(task)           |
  kfree(task-&amp;amp;gt;slow_task) //FREE|
                               |  task-&amp;amp;gt;slow_task-&amp;amp;gt;... //USE&lt;/p&gt;
&lt;p&gt;Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure
the timer handler have finished before the &amp;amp;quot;task-&amp;amp;gt;slow_task&amp;amp;quot; is
deallocated.(CVE-2022-50422)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ppp: associate skb with a device at tx&lt;/p&gt;
&lt;p&gt;Syzkaller triggered flow dissector warning with the following:&lt;/p&gt;
&lt;p&gt;r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;amp;(0x7f0000000000), 0xc0802, 0x0)
ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;amp;(0x7f00000000c0))
ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;amp;(0x7f0000000240)={0x2, &amp;amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]})
pwritev(r0, &amp;amp;amp;(0x7f0000…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()&lt;/p&gt;
&lt;p&gt;When executing SMP task failed, the smp_execute_task_sg() calls del_timer()
to delete &amp;amp;quot;slow_task-&amp;amp;gt;timer&amp;amp;quot;. However, if the timer handler
sas_task_internal_timedout() is running, the del_timer() in
smp_execute_task_sg() will not stop it and a UAF will happen. The process
is shown below:&lt;/p&gt;
&lt;p&gt;(thread 1)               |        (thread 2)
smp_execute_task_sg()          | sas_task_internal_timedout()
 ...                           |
 del_timer()                   |
 ...                           |  ...
 sas_free_task(task)           |
  kfree(task-&amp;amp;gt;slow_task) //FREE|
                               |  task-&amp;amp;gt;slow_task-&amp;amp;gt;... //USE&lt;/p&gt;
&lt;p&gt;Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure
the timer handler have finished before the &amp;amp;quot;task-&amp;amp;gt;slow_task&amp;amp;quot; is
deallocated.(CVE-2022-50422)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ppp: associate skb with a device at tx&lt;/p&gt;
&lt;p&gt;Syzkaller triggered flow dissector warning with the following:&lt;/p&gt;
&lt;p&gt;r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;amp;(0x7f0000000000), 0xc0802, 0x0)
ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;amp;(0x7f00000000c0))
ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;amp;(0x7f0000000240)={0x2, &amp;amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]})
pwritev(r0, &amp;amp;amp;(0x7f0000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-1231</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50655</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50655</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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ppp: associate skb with a device at tx Syzkaller triggered flow dissector warning with the following: r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;(0x7f0000000000), 0xc0802, 0x0) ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;(0x7f00000000c0)) ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;(0x7f0000000240)={0x2, &amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]}) pwritev(r0, &amp;amp;(0x7f0000000040)=[{&amp;amp;(0x7f0000000140)=&amp;#39;\x00!&amp;#39;, 0x2}], 0x1, 0x0, 0x0) [    9.485814] WARNING: CPU: 3 PID: 329 at net/core/flow_dissector.c:1016 __skb_flow_dissect+0x1ee0/0x1fa0 [    9.485929]  skb_get_poff+0x53/0xa0 [    9.485937]  bpf_skb_get_pay_offset+0xe/0x20 [    9.485944]  ? ppp_send_frame+0xc2/0x5b0 [    9.485949]  ? _raw_spin_unlock_irqrestore+0x40/0x60 [    9.485958]  ? __ppp_xmit_process+0x7a/0xe0 [    9.485968]  ? ppp_xmit_process+0x5b/0xb0 [    9.485974]  ? ppp_write+0x12a/0x190 [    9.485981]  ? do_iter_write+0x18e/0x2d0 [    9.485987]  ? __import_iovec+0x30/0x130 [    9.485997]  ? do_pwritev+0x1b6/0x240 [    9.486016]  ? trace_hardirqs_on+0x47/0x50 [    9.486023]  ? __x64_sys_pwritev+0x24/0x30 [    9.486026]  ? do_syscall_64+0x3d/0x80 [    9.486031]  ? entry_SYSCALL_64_after_hwframe+0x63/0xcd Flow dissector tries to find skb net namespace either via device or via socket. Neigher is set in ppp_send_frame, so let&amp;#39;s manually use ppp-&amp;gt;dev.&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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ppp: associate skb with a device at tx Syzkaller triggered flow dissector warning with the following: r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;(0x7f0000000000), 0xc0802, 0x0) ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;(0x7f00000000c0)) ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;(0x7f0000000240)={0x2, &amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]}) pwritev(r0, &amp;amp;(0x7f0000000040)=[{&amp;amp;(0x7f0000000140)=&amp;#39;\x00!&amp;#39;, 0x2}], 0x1, 0x0, 0x0) [    9.485814] WARNING: CPU: 3 PID: 329 at net/core/flow_dissector.c:1016 __skb_flow_dissect+0x1ee0/0x1fa0 [    9.485929]  skb_get_poff+0x53/0xa0 [    9.485937]  bpf_skb_get_pay_offset+0xe/0x20 [    9.485944]  ? ppp_send_frame+0xc2/0x5b0 [    9.485949]  ? _raw_spin_unlock_irqrestore+0x40/0x60 [    9.485958]  ? __ppp_xmit_process+0x7a/0xe0 [    9.485968]  ? ppp_xmit_process+0x5b/0xb0 [    9.485974]  ? ppp_write+0x12a/0x190 [    9.485981]  ? do_iter_write+0x18e/0x2d0 [    9.485987]  ? __import_iovec+0x30/0x130 [    9.485997]  ? do_pwritev+0x1b6/0x240 [    9.486016]  ? trace_hardirqs_on+0x47/0x50 [    9.486023]  ? __x64_sys_pwritev+0x24/0x30 [    9.486026]  ? do_syscall_64+0x3d/0x80 [    9.486031]  ? entry_SYSCALL_64_after_hwframe+0x63/0xcd Flow dissector tries to find skb net namespace either via device or via socket. Neigher is set in ppp_send_frame, so let&amp;#39;s manually use ppp-&amp;gt;dev.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50655</guid>
    </item>
  </channel>
</rss>
