<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 15:46:44 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97619</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97619</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/rw: end write accounting from -&amp;gt;ki_complete&lt;/p&gt;
&lt;p&gt;Commit b000145e9907 moved both the fsnotify calls and the write
accounting out of the kiocb completion handler and into the
io_req_rw_complete() task_work. However, only the fsnotify part actually
needed to move as it may sleep. Ending the write accounting is just a
percpu_up_read() on the superblock writers sem.&lt;/p&gt;
&lt;p&gt;Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE
protection depend on the ring owner getting to running task_work. But
the task may be blocked in freeze_super(), causing it to never get to
that:&lt;/p&gt;
&lt;p&gt;task                             io-wq worker
  --------------------------------------------------------------
  io_write()
    io_kiocb_start_write()         (takes sb_writers, hidden from
                                    lockdep by __sb_writers_release)
    write_iter() -&amp;gt; -EIOCBQUEUED
  ioctl(FS_IOC_SHUTDOWN)
    bdev_freeze()
      freeze_super()
        percpu_down_write()        &amp;lt;- waits for the reader above
                                   io_write()
                                     kiocb_start_write()
                                       percpu_down_read()  &amp;lt;- queued
                                                              behind the
                                                              writer
  &amp;lt;bio completes&amp;gt;
    io_complete_rw()
      queues io_req_rw_complete()  &amp;lt;- never runs, task is in D state…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/rw: end write accounting from -&amp;gt;ki_complete&lt;/p&gt;
&lt;p&gt;Commit b000145e9907 moved both the fsnotify calls and the write
accounting out of the kiocb completion handler and into the
io_req_rw_complete() task_work. However, only the fsnotify part actually
needed to move as it may sleep. Ending the write accounting is just a
percpu_up_read() on the superblock writers sem.&lt;/p&gt;
&lt;p&gt;Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE
protection depend on the ring owner getting to running task_work. But
the task may be blocked in freeze_super(), causing it to never get to
that:&lt;/p&gt;
&lt;p&gt;task                             io-wq worker
  --------------------------------------------------------------
  io_write()
    io_kiocb_start_write()         (takes sb_writers, hidden from
                                    lockdep by __sb_writers_release)
    write_iter() -&amp;gt; -EIOCBQUEUED
  ioctl(FS_IOC_SHUTDOWN)
    bdev_freeze()
      freeze_super()
        percpu_down_write()        &amp;lt;- waits for the reader above
                                   io_write()
                                     kiocb_start_write()
                                       percpu_down_read()  &amp;lt;- queued
                                                              behind the
                                                              writer
  &amp;lt;bio completes&amp;gt;
    io_complete_rw()
      queues io_req_rw_complete()  &amp;lt;- never runs, task is in D state…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97619</guid>
    </item>
    <item>
      <title>GHSA-rr3w-gg4f-957r</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-rr3w-gg4f-957r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/rw: end write accounting from -&amp;gt;ki_complete&lt;/p&gt;
&lt;p&gt;Commit b000145e9907 moved both the fsnotify calls and the write
accounting out of the kiocb completion handler and into the
io_req_rw_complete() task_work. However, only the fsnotify part actually
needed to move as it may sleep. Ending the write accounting is just a
percpu_up_read() on the superblock writers sem.&lt;/p&gt;
&lt;p&gt;Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE
protection depend on the ring owner getting to running task_work. But
the task may be blocked in freeze_super(), causing it to never get to
that:&lt;/p&gt;
&lt;p&gt;task                             io-wq worker
  --------------------------------------------------------------
  io_write()
    io_kiocb_start_write()         (takes sb_writers, hidden from
                                    lockdep by __sb_writers_release)
    write_iter() -&amp;gt; -EIOCBQUEUED
  ioctl(FS_IOC_SHUTDOWN)
    bdev_freeze()
      freeze_super()
        percpu_down_write()        &amp;lt;- waits for the reader above
                                   io_write()
                                     kiocb_start_write()
                                       percpu_down_read()  &amp;lt;- queued
                                                              behind the
                                                              writer
  &amp;lt;bio completes&amp;gt;
    io_complete_rw()
      queues io_req_rw_complete()  &amp;lt;- never runs, task is in D state…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/rw: end write accounting from -&amp;gt;ki_complete&lt;/p&gt;
&lt;p&gt;Commit b000145e9907 moved both the fsnotify calls and the write
accounting out of the kiocb completion handler and into the
io_req_rw_complete() task_work. However, only the fsnotify part actually
needed to move as it may sleep. Ending the write accounting is just a
percpu_up_read() on the superblock writers sem.&lt;/p&gt;
&lt;p&gt;Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE
protection depend on the ring owner getting to running task_work. But
the task may be blocked in freeze_super(), causing it to never get to
that:&lt;/p&gt;
&lt;p&gt;task                             io-wq worker
  --------------------------------------------------------------
  io_write()
    io_kiocb_start_write()         (takes sb_writers, hidden from
                                    lockdep by __sb_writers_release)
    write_iter() -&amp;gt; -EIOCBQUEUED
  ioctl(FS_IOC_SHUTDOWN)
    bdev_freeze()
      freeze_super()
        percpu_down_write()        &amp;lt;- waits for the reader above
                                   io_write()
                                     kiocb_start_write()
                                       percpu_down_read()  &amp;lt;- queued
                                                              behind the
                                                              writer
  &amp;lt;bio completes&amp;gt;
    io_complete_rw()
      queues io_req_rw_complete()  &amp;lt;- never runs, task is in D state…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-rr3w-gg4f-957r</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97619</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97619</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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/rw: end write accounting from -&amp;gt;ki_complete Commit b000145e9907 moved both the fsnotify calls and the write accounting out of the kiocb completion handler and into the io_req_rw_complete() task_work. However, only the fsnotify part actually needed to move as it may sleep. Ending the write accounting is just a percpu_up_read() on the superblock writers sem. Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE protection depend on the ring owner getting to running task_work. But the task may be blocked in freeze_super(), causing it to never get to that:   task                             io-wq worker   --------------------------------------------------------------   io_write()     io_kiocb_start_write()         (takes sb_writers, hidden from                                     lockdep by __sb_writers_release)     write_iter() -&amp;gt; -EIOCBQUEUED   ioctl(FS_IOC_SHUTDOWN)     bdev_freeze()       freeze_super()         percpu_down_write()        &amp;lt;- waits for the reader above                                    io_write()                                      kiocb_start_write()                                        percpu_down_read()  &amp;lt;- queued                                                               behind the                                                               writer   &amp;lt;bio completes&amp;gt;     io_complete_rw()       queues io_req_rw_complete()  &amp;lt;- never runs, task is in D state End…&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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/rw: end write accounting from -&amp;gt;ki_complete Commit b000145e9907 moved both the fsnotify calls and the write accounting out of the kiocb completion handler and into the io_req_rw_complete() task_work. However, only the fsnotify part actually needed to move as it may sleep. Ending the write accounting is just a percpu_up_read() on the superblock writers sem. Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE protection depend on the ring owner getting to running task_work. But the task may be blocked in freeze_super(), causing it to never get to that:   task                             io-wq worker   --------------------------------------------------------------   io_write()     io_kiocb_start_write()         (takes sb_writers, hidden from                                     lockdep by __sb_writers_release)     write_iter() -&amp;gt; -EIOCBQUEUED   ioctl(FS_IOC_SHUTDOWN)     bdev_freeze()       freeze_super()         percpu_down_write()        &amp;lt;- waits for the reader above                                    io_write()                                      kiocb_start_write()                                        percpu_down_read()  &amp;lt;- queued                                                               behind the                                                               writer   &amp;lt;bio completes&amp;gt;     io_complete_rw()       queues io_req_rw_complete()  &amp;lt;- never runs, task is in D state End…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97619</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
