<?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://cve.radiocsirt.org</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, 03 Oct 2026 17:12:50 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:6567 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:6567</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
  * kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
  * kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
  * kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
  * kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
  * kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
  * kernel: KVM: SVM: Flush pages under kvm-&amp;amp;gt;lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
  * kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
  * kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
  * kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
  * kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
  * kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
  * kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
  * kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
  * kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
  * kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
  * kernel: xhci: Handle TD clearing fo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 52 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
  * kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
  * kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
  * kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
  * kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
  * kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
  * kernel: KVM: SVM: Flush pages under kvm-&amp;amp;gt;lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
  * kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
  * kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
  * kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
  * kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
  * kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
  * kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
  * kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
  * kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
  * kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
  * kernel: xhci: Handle TD clearing fo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:6567</guid>
    </item>
    <item>
      <title>bdu:2024-03757</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03757</link>
      <description>bdu:2024-03757</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03757</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26630</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26630</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-26630</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0777 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0777</link>
      <description>certfr-2024-avi-0777</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0777</guid>
    </item>
    <item>
      <title>EUVD-2026-345470</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345470</link>
      <description>EUVD-2026-345470</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345470</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26630</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26630</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: cachestat: fix folio read-after-free in cache walk&lt;/p&gt;
&lt;p&gt;In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute
its page offset, and check for its dirty and writeback flags.  However, we
do not hold a reference to the folio before performing these actions,
which means the folio can concurrently be released and reused as another
folio/page/slab.&lt;/p&gt;
&lt;p&gt;Get around this altogether by just using xarray&amp;#39;s existing machinery for
the folio page offsets and dirty/writeback states.&lt;/p&gt;
&lt;p&gt;This changes behavior for tmpfs files to now always report zeroes in their
dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow
conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during
swapout, after which they&amp;#39;re no longer resident etc.&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;mm: cachestat: fix folio read-after-free in cache walk&lt;/p&gt;
&lt;p&gt;In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute
its page offset, and check for its dirty and writeback flags.  However, we
do not hold a reference to the folio before performing these actions,
which means the folio can concurrently be released and reused as another
folio/page/slab.&lt;/p&gt;
&lt;p&gt;Get around this altogether by just using xarray&amp;#39;s existing machinery for
the folio page offsets and dirty/writeback states.&lt;/p&gt;
&lt;p&gt;This changes behavior for tmpfs files to now always report zeroes in their
dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow
conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during
swapout, after which they&amp;#39;re no longer resident etc.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26630</guid>
    </item>
    <item>
      <title>GHSA-8h7v-x635-x447</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8h7v-x635-x447</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: cachestat: fix folio read-after-free in cache walk&lt;/p&gt;
&lt;p&gt;In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute
its page offset, and check for its dirty and writeback flags.  However, we
do not hold a reference to the folio before performing these actions,
which means the folio can concurrently be released and reused as another
folio/page/slab.&lt;/p&gt;
&lt;p&gt;Get around this altogether by just using xarray&amp;#39;s existing machinery for
the folio page offsets and dirty/writeback states.&lt;/p&gt;
&lt;p&gt;This changes behavior for tmpfs files to now always report zeroes in their
dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow
conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during
swapout, after which they&amp;#39;re no longer resident etc.&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;mm: cachestat: fix folio read-after-free in cache walk&lt;/p&gt;
&lt;p&gt;In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute
its page offset, and check for its dirty and writeback flags.  However, we
do not hold a reference to the folio before performing these actions,
which means the folio can concurrently be released and reused as another
folio/page/slab.&lt;/p&gt;
&lt;p&gt;Get around this altogether by just using xarray&amp;#39;s existing machinery for
the folio page offsets and dirty/writeback states.&lt;/p&gt;
&lt;p&gt;This changes behavior for tmpfs files to now always report zeroes in their
dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow
conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during
swapout, after which they&amp;#39;re no longer resident etc.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8h7v-x635-x447</guid>
    </item>
    <item>
      <title>gsd-2024-26630</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26630</link>
      <description>gsd-2024-26630</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26630</guid>
    </item>
    <item>
      <title>RHSA-2024:6567 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:6567</link>
      <description>&lt;p&gt;kernel: efivarfs: force RO when remounting if SetVariable is not supported kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area kernel: nfsd: fix RELEASE_LOCKOWNER kernel: mm: cachestat: fix folio read-after-free in cache walk kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again kernel: Bluetooth: af_bluetooth: Fix deadlock kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address kernel: KVM: SVM: Flush pages under kvm-&amp;amp;gt;lock to fix UAF in svm_register_enc_region() kernel: mm: cachestat: fix two shmem bugs kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() kernel: net: fix out-of-bounds access in ops_init kernel: net: bridge: mst: fix vlan use-after-free kernel: scsi: qedf: Ensure the copied buf is NUL terminated kernel: usb-storage: alauda: Check whether the media is initialized kernel: xhci: Handle TD clearing for multiple streams case kernel: cxl/region: Fix memregion leaks in devm_cxl_add_region() kernel: net/sched: Fix UAF when resolving a clash kernel: ppp: reject claimed-as-LCP but actually malformed packets kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() kernel: nvme: avoid double free special payload kernel: PCI/MSI: Fix UAF in msi_capability_init kernel: xdp: Remove WARN() from __xdp_reg_mem_model() kernel: x86: stop playing stack…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: efivarfs: force RO when remounting if SetVariable is not supported kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area kernel: nfsd: fix RELEASE_LOCKOWNER kernel: mm: cachestat: fix folio read-after-free in cache walk kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again kernel: Bluetooth: af_bluetooth: Fix deadlock kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address kernel: KVM: SVM: Flush pages under kvm-&amp;amp;gt;lock to fix UAF in svm_register_enc_region() kernel: mm: cachestat: fix two shmem bugs kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() kernel: net: fix out-of-bounds access in ops_init kernel: net: bridge: mst: fix vlan use-after-free kernel: scsi: qedf: Ensure the copied buf is NUL terminated kernel: usb-storage: alauda: Check whether the media is initialized kernel: xhci: Handle TD clearing for multiple streams case kernel: cxl/region: Fix memregion leaks in devm_cxl_add_region() kernel: net/sched: Fix UAF when resolving a clash kernel: ppp: reject claimed-as-LCP but actually malformed packets kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() kernel: nvme: avoid double free special payload kernel: PCI/MSI: Fix UAF in msi_capability_init kernel: xdp: Remove WARN() from __xdp_reg_mem_model() kernel: x86: stop playing stack…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:6567</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26630</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26630</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.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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: cachestat: fix folio read-after-free in cache walk In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute its page offset, and check for its dirty and writeback flags.  However, we do not hold a reference to the folio before performing these actions, which means the folio can concurrently be released and reused as another folio/page/slab. Get around this altogether by just using xarray&amp;#39;s existing machinery for the folio page offsets and dirty/writeback states. This changes behavior for tmpfs files to now always report zeroes in their dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during swapout, after which they&amp;#39;re no longer resident etc.&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.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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm: cachestat: fix folio read-after-free in cache walk In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute its page offset, and check for its dirty and writeback flags.  However, we do not hold a reference to the folio before performing these actions, which means the folio can concurrently be released and reused as another folio/page/slab. Get around this altogether by just using xarray&amp;#39;s existing machinery for the folio page offsets and dirty/writeback states. This changes behavior for tmpfs files to now always report zeroes in their dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during swapout, after which they&amp;#39;re no longer resident etc.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26630</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0632 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0632</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service 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 Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0632</guid>
    </item>
  </channel>
</rss>
