<?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>Fri, 02 Oct 2026 19:42:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05844</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05844</link>
      <description>bdu:2026-05844</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05844</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-310877</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310877</link>
      <description>EUVD-2026-310877</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310877</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49874</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49874</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hyperv: fix possible memory leak in mousevsc_probe()&lt;/p&gt;
&lt;p&gt;If hid_add_device() returns error, it should call hid_destroy_device()
to free hid_dev which is allocated in hid_allocate_device().&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;HID: hyperv: fix possible memory leak in mousevsc_probe()&lt;/p&gt;
&lt;p&gt;If hid_add_device() returns error, it should call hid_destroy_device()
to free hid_dev which is allocated in hid_allocate_device().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49874</guid>
    </item>
    <item>
      <title>GHSA-5q7j-4fw2-f268</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5q7j-4fw2-f268</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hyperv: fix possible memory leak in mousevsc_probe()&lt;/p&gt;
&lt;p&gt;If hid_add_device() returns error, it should call hid_destroy_device()
to free hid_dev which is allocated in hid_allocate_device().&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;HID: hyperv: fix possible memory leak in mousevsc_probe()&lt;/p&gt;
&lt;p&gt;If hid_add_device() returns error, it should call hid_destroy_device()
to free hid_dev which is allocated in hid_allocate_device().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5q7j-4fw2-f268</guid>
    </item>
    <item>
      <title>OESA-2025-1569 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1569</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;gfs2: Check sb_bsize_shift after reading superblock&lt;/p&gt;
&lt;p&gt;Fuzzers like to scribble over sb_bsize_shift but in reality it&amp;amp;apos;s very
unlikely that this field would be corrupted on its own. Nevertheless it
should be checked to avoid the possibility of messy mount errors due to
bad calculations. It&amp;amp;apos;s always a fixed value based on the block size so
we can just check that it&amp;amp;apos;s the expected value.&lt;/p&gt;
&lt;p&gt;Tested with:&lt;/p&gt;
&lt;p&gt;mkfs.gfs2 -O -p lock_nolock /dev/vdb
    for i in 0 -1 64 65 32 33; do
        gfs2_edit -p sb field sb_bsize_shift $i /dev/vdb
        mount /dev/vdb /mnt/test &amp;amp;amp;&amp;amp;amp; umount /mnt/test
    done&lt;/p&gt;
&lt;p&gt;Before this patch we get a withdraw after&lt;/p&gt;
&lt;p&gt;[   76.413681] gfs2: fsid=loop0.0: fatal: invalid metadata block
[   76.413681]   bh = 19 (type: exp=5, found=4)
[   76.413681]   function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 492&lt;/p&gt;
&lt;p&gt;and with UBSAN configured we also get complaints like&lt;/p&gt;
&lt;p&gt;[   76.373395] UBSAN: shift-out-of-bounds in fs/gfs2/ops_fstype.c:295:19
[   76.373815] shift exponent 4294967287 is too large for 64-bit type &amp;amp;apos;long unsigned int&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;After the patch, these complaints don&amp;amp;apos;t appear, mount fails immediately
and we get an explanation in dmesg.(CVE-2022-49769)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram()&lt;/p&gt;
&lt;p&gt;`s…&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;gfs2: Check sb_bsize_shift after reading superblock&lt;/p&gt;
&lt;p&gt;Fuzzers like to scribble over sb_bsize_shift but in reality it&amp;amp;apos;s very
unlikely that this field would be corrupted on its own. Nevertheless it
should be checked to avoid the possibility of messy mount errors due to
bad calculations. It&amp;amp;apos;s always a fixed value based on the block size so
we can just check that it&amp;amp;apos;s the expected value.&lt;/p&gt;
&lt;p&gt;Tested with:&lt;/p&gt;
&lt;p&gt;mkfs.gfs2 -O -p lock_nolock /dev/vdb
    for i in 0 -1 64 65 32 33; do
        gfs2_edit -p sb field sb_bsize_shift $i /dev/vdb
        mount /dev/vdb /mnt/test &amp;amp;amp;&amp;amp;amp; umount /mnt/test
    done&lt;/p&gt;
&lt;p&gt;Before this patch we get a withdraw after&lt;/p&gt;
&lt;p&gt;[   76.413681] gfs2: fsid=loop0.0: fatal: invalid metadata block
[   76.413681]   bh = 19 (type: exp=5, found=4)
[   76.413681]   function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 492&lt;/p&gt;
&lt;p&gt;and with UBSAN configured we also get complaints like&lt;/p&gt;
&lt;p&gt;[   76.373395] UBSAN: shift-out-of-bounds in fs/gfs2/ops_fstype.c:295:19
[   76.373815] shift exponent 4294967287 is too large for 64-bit type &amp;amp;apos;long unsigned int&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;After the patch, these complaints don&amp;amp;apos;t appear, mount fails immediately
and we get an explanation in dmesg.(CVE-2022-49769)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram()&lt;/p&gt;
&lt;p&gt;`s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1569</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49874</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49874</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: hyperv: fix possible memory leak in mousevsc_probe() If hid_add_device() returns error, it should call hid_destroy_device() to free hid_dev which is allocated in hid_allocate_device().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: hyperv: fix possible memory leak in mousevsc_probe() If hid_add_device() returns error, it should call hid_destroy_device() to free hid_dev which is allocated in hid_allocate_device().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49874</guid>
    </item>
  </channel>
</rss>
