https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:42:10 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46183 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2026-46183 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-327162 EUVD-2026-327162 https://cve.radiocsirt.org/vuln/euvd-2026-327162 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46183 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock</p> <p>damon_sysfs_quot_goal-&gt;path can be read and written by users, via DAMON sysfs &#39;path&#39; file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don&#39;t race when the same open file is used by the writer, due to kernfs&#39;s open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock</p> <p>damon_sysfs_quot_goal-&gt;path can be read and written by users, via DAMON sysfs &#39;path&#39; file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don&#39;t race when the same open file is used by the writer, due to kernfs&#39;s open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46183 https://cve.radiocsirt.org/vuln/ghsa-82v4-79hw-3g4g <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock</p> <p>damon_sysfs_quot_goal-&gt;path can be read and written by users, via DAMON sysfs &#39;path&#39; file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don&#39;t race when the same open file is used by the writer, due to kernfs&#39;s open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock</p> <p>damon_sysfs_quot_goal-&gt;path can be read and written by users, via DAMON sysfs &#39;path&#39; file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don&#39;t race when the same open file is used by the writer, due to kernfs&#39;s open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.</p> https://cve.radiocsirt.org/vuln/ghsa-82v4-79hw-3g4g https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 <p>kernel-devel-7.0.11-1.1 on GA media</p> <p>kernel-devel-7.0.11-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46183 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 106 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock damon_sysfs_quot_goal-&gt;path can be read and written by users, via DAMON sysfs &#39;path&#39; file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don&#39;t race when the same open file is used by the writer, due to kernfs&#39;s open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 106 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock damon_sysfs_quot_goal-&gt;path can be read and written by users, via DAMON sysfs &#39;path&#39; file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don&#39;t race when the same open file is used by the writer, due to kernfs&#39;s open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46183 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700