<?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 02:25:22 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03269</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03269</link>
      <description>bdu:2026-03269</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03269</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-310794</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310794</link>
      <description>EUVD-2026-310794</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310794</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49771</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49771</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm ioctl: fix misbehavior if list_versions races with module loading&lt;/p&gt;
&lt;p&gt;__list_versions will first estimate the required space using the
&amp;#34;dm_target_iterate(list_version_get_needed, &amp;amp;needed)&amp;#34; call and then will
fill the space using the &amp;#34;dm_target_iterate(list_version_get_info,
&amp;amp;iter_info)&amp;#34; call. Each of these calls locks the targets using the
&amp;#34;down_read(&amp;amp;_lock)&amp;#34; and &amp;#34;up_read(&amp;amp;_lock)&amp;#34; calls, however between the first
and second &amp;#34;dm_target_iterate&amp;#34; there is no lock held and the target
modules can be loaded at this point, so the second &amp;#34;dm_target_iterate&amp;#34;
call may need more space than what was the first &amp;#34;dm_target_iterate&amp;#34;
returned.&lt;/p&gt;
&lt;p&gt;The code tries to handle this overflow (see the beginning of
list_version_get_info), however this handling is incorrect.&lt;/p&gt;
&lt;p&gt;The code sets &amp;#34;param-&amp;gt;data_size = param-&amp;gt;data_start + needed&amp;#34; and
&amp;#34;iter_info.end = (char *)vers+len&amp;#34; - &amp;#34;needed&amp;#34; is the size returned by the
first dm_target_iterate call; &amp;#34;len&amp;#34; is the size of the buffer allocated by
userspace.&lt;/p&gt;
&lt;p&gt;&amp;#34;len&amp;#34; may be greater than &amp;#34;needed&amp;#34;; in this case, the code will write up
to &amp;#34;len&amp;#34; bytes into the buffer, however param-&amp;gt;data_size is set to
&amp;#34;needed&amp;#34;, so it may write data past the param-&amp;gt;data_size value. The ioctl
interface copies only up to param-&amp;gt;data_size into userspace, thus part of
the result will be truncated.&lt;/p&gt;
&lt;p&gt;Fix this bug by setting &amp;#34;iter_info.end = (char *)vers + needed;&amp;#34; - this
guarantees that the second &amp;#34;dm_target_iterate&amp;#34; call wi…&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;dm ioctl: fix misbehavior if list_versions races with module loading&lt;/p&gt;
&lt;p&gt;__list_versions will first estimate the required space using the
&amp;#34;dm_target_iterate(list_version_get_needed, &amp;amp;needed)&amp;#34; call and then will
fill the space using the &amp;#34;dm_target_iterate(list_version_get_info,
&amp;amp;iter_info)&amp;#34; call. Each of these calls locks the targets using the
&amp;#34;down_read(&amp;amp;_lock)&amp;#34; and &amp;#34;up_read(&amp;amp;_lock)&amp;#34; calls, however between the first
and second &amp;#34;dm_target_iterate&amp;#34; there is no lock held and the target
modules can be loaded at this point, so the second &amp;#34;dm_target_iterate&amp;#34;
call may need more space than what was the first &amp;#34;dm_target_iterate&amp;#34;
returned.&lt;/p&gt;
&lt;p&gt;The code tries to handle this overflow (see the beginning of
list_version_get_info), however this handling is incorrect.&lt;/p&gt;
&lt;p&gt;The code sets &amp;#34;param-&amp;gt;data_size = param-&amp;gt;data_start + needed&amp;#34; and
&amp;#34;iter_info.end = (char *)vers+len&amp;#34; - &amp;#34;needed&amp;#34; is the size returned by the
first dm_target_iterate call; &amp;#34;len&amp;#34; is the size of the buffer allocated by
userspace.&lt;/p&gt;
&lt;p&gt;&amp;#34;len&amp;#34; may be greater than &amp;#34;needed&amp;#34;; in this case, the code will write up
to &amp;#34;len&amp;#34; bytes into the buffer, however param-&amp;gt;data_size is set to
&amp;#34;needed&amp;#34;, so it may write data past the param-&amp;gt;data_size value. The ioctl
interface copies only up to param-&amp;gt;data_size into userspace, thus part of
the result will be truncated.&lt;/p&gt;
&lt;p&gt;Fix this bug by setting &amp;#34;iter_info.end = (char *)vers + needed;&amp;#34; - this
guarantees that the second &amp;#34;dm_target_iterate&amp;#34; call wi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49771</guid>
    </item>
    <item>
      <title>GHSA-qp86-w2fg-h37h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qp86-w2fg-h37h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm ioctl: fix misbehavior if list_versions races with module loading&lt;/p&gt;
&lt;p&gt;__list_versions will first estimate the required space using the
&amp;#34;dm_target_iterate(list_version_get_needed, &amp;amp;needed)&amp;#34; call and then will
fill the space using the &amp;#34;dm_target_iterate(list_version_get_info,
&amp;amp;iter_info)&amp;#34; call. Each of these calls locks the targets using the
&amp;#34;down_read(&amp;amp;_lock)&amp;#34; and &amp;#34;up_read(&amp;amp;_lock)&amp;#34; calls, however between the first
and second &amp;#34;dm_target_iterate&amp;#34; there is no lock held and the target
modules can be loaded at this point, so the second &amp;#34;dm_target_iterate&amp;#34;
call may need more space than what was the first &amp;#34;dm_target_iterate&amp;#34;
returned.&lt;/p&gt;
&lt;p&gt;The code tries to handle this overflow (see the beginning of
list_version_get_info), however this handling is incorrect.&lt;/p&gt;
&lt;p&gt;The code sets &amp;#34;param-&amp;gt;data_size = param-&amp;gt;data_start + needed&amp;#34; and
&amp;#34;iter_info.end = (char *)vers+len&amp;#34; - &amp;#34;needed&amp;#34; is the size returned by the
first dm_target_iterate call; &amp;#34;len&amp;#34; is the size of the buffer allocated by
userspace.&lt;/p&gt;
&lt;p&gt;&amp;#34;len&amp;#34; may be greater than &amp;#34;needed&amp;#34;; in this case, the code will write up
to &amp;#34;len&amp;#34; bytes into the buffer, however param-&amp;gt;data_size is set to
&amp;#34;needed&amp;#34;, so it may write data past the param-&amp;gt;data_size value. The ioctl
interface copies only up to param-&amp;gt;data_size into userspace, thus part of
the result will be truncated.&lt;/p&gt;
&lt;p&gt;Fix this bug by setting &amp;#34;iter_info.end = (char *)vers + needed;&amp;#34; - this
guarantees that the second &amp;#34;dm_target_iterate&amp;#34; call wi…&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;dm ioctl: fix misbehavior if list_versions races with module loading&lt;/p&gt;
&lt;p&gt;__list_versions will first estimate the required space using the
&amp;#34;dm_target_iterate(list_version_get_needed, &amp;amp;needed)&amp;#34; call and then will
fill the space using the &amp;#34;dm_target_iterate(list_version_get_info,
&amp;amp;iter_info)&amp;#34; call. Each of these calls locks the targets using the
&amp;#34;down_read(&amp;amp;_lock)&amp;#34; and &amp;#34;up_read(&amp;amp;_lock)&amp;#34; calls, however between the first
and second &amp;#34;dm_target_iterate&amp;#34; there is no lock held and the target
modules can be loaded at this point, so the second &amp;#34;dm_target_iterate&amp;#34;
call may need more space than what was the first &amp;#34;dm_target_iterate&amp;#34;
returned.&lt;/p&gt;
&lt;p&gt;The code tries to handle this overflow (see the beginning of
list_version_get_info), however this handling is incorrect.&lt;/p&gt;
&lt;p&gt;The code sets &amp;#34;param-&amp;gt;data_size = param-&amp;gt;data_start + needed&amp;#34; and
&amp;#34;iter_info.end = (char *)vers+len&amp;#34; - &amp;#34;needed&amp;#34; is the size returned by the
first dm_target_iterate call; &amp;#34;len&amp;#34; is the size of the buffer allocated by
userspace.&lt;/p&gt;
&lt;p&gt;&amp;#34;len&amp;#34; may be greater than &amp;#34;needed&amp;#34;; in this case, the code will write up
to &amp;#34;len&amp;#34; bytes into the buffer, however param-&amp;gt;data_size is set to
&amp;#34;needed&amp;#34;, so it may write data past the param-&amp;gt;data_size value. The ioctl
interface copies only up to param-&amp;gt;data_size into userspace, thus part of
the result will be truncated.&lt;/p&gt;
&lt;p&gt;Fix this bug by setting &amp;#34;iter_info.end = (char *)vers + needed;&amp;#34; - this
guarantees that the second &amp;#34;dm_target_iterate&amp;#34; call wi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qp86-w2fg-h37h</guid>
    </item>
    <item>
      <title>OESA-2025-1513 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1513</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;Bluetooth: Fix use after free in hci_send_acl&lt;/p&gt;
&lt;p&gt;This fixes the following trace caused by receiving
HCI_EV_DISCONN_PHY_LINK_COMPLETE which does call hci_conn_del without
first checking if conn-&amp;amp;gt;type is in fact AMP_LINK and in case it is
do properly cleanup upper layers with hci_disconn_cfm:&lt;/p&gt;
&lt;p&gt;==================================================================
    BUG: KASAN: use-after-free in hci_send_acl+0xaba/0xc50
    Read of size 8 at addr ffff88800e404818 by task bluetoothd/142&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 142 Comm: bluetoothd Not tainted
    5.17.0-rc5-00006-gda4022eeac1a #7
    Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
    rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
    Call Trace:
     &amp;amp;lt;TASK&amp;amp;gt;
     dump_stack_lvl+0x45/0x59
     print_address_description.constprop.0+0x1f/0x150
     kasan_report.cold+0x7f/0x11b
     hci_send_acl+0xaba/0xc50
     l2cap_do_send+0x23f/0x3d0
     l2cap_chan_send+0xc06/0x2cc0
     l2cap_sock_sendmsg+0x201/0x2b0
     sock_sendmsg+0xdc/0x110
     sock_write_iter+0x20f/0x370
     do_iter_readv_writev+0x343/0x690
     do_iter_write+0x132/0x640
     vfs_writev+0x198/0x570
     do_writev+0x202/0x280
     do_syscall_64+0x38/0x90
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RSP: 002b:00007ffce8a099b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
    Code: 0f 00 f7 d8 64 89 02 48 c7…&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;Bluetooth: Fix use after free in hci_send_acl&lt;/p&gt;
&lt;p&gt;This fixes the following trace caused by receiving
HCI_EV_DISCONN_PHY_LINK_COMPLETE which does call hci_conn_del without
first checking if conn-&amp;amp;gt;type is in fact AMP_LINK and in case it is
do properly cleanup upper layers with hci_disconn_cfm:&lt;/p&gt;
&lt;p&gt;==================================================================
    BUG: KASAN: use-after-free in hci_send_acl+0xaba/0xc50
    Read of size 8 at addr ffff88800e404818 by task bluetoothd/142&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 142 Comm: bluetoothd Not tainted
    5.17.0-rc5-00006-gda4022eeac1a #7
    Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
    rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
    Call Trace:
     &amp;amp;lt;TASK&amp;amp;gt;
     dump_stack_lvl+0x45/0x59
     print_address_description.constprop.0+0x1f/0x150
     kasan_report.cold+0x7f/0x11b
     hci_send_acl+0xaba/0xc50
     l2cap_do_send+0x23f/0x3d0
     l2cap_chan_send+0xc06/0x2cc0
     l2cap_sock_sendmsg+0x201/0x2b0
     sock_sendmsg+0xdc/0x110
     sock_write_iter+0x20f/0x370
     do_iter_readv_writev+0x343/0x690
     do_iter_write+0x132/0x640
     vfs_writev+0x198/0x570
     do_writev+0x202/0x280
     do_syscall_64+0x38/0x90
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RSP: 002b:00007ffce8a099b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
    Code: 0f 00 f7 d8 64 89 02 48 c7…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1513</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-49771</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49771</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 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm ioctl: fix misbehavior if list_versions races with module loading __list_versions will first estimate the required space using the &amp;#34;dm_target_iterate(list_version_get_needed, &amp;amp;needed)&amp;#34; call and then will fill the space using the &amp;#34;dm_target_iterate(list_version_get_info, &amp;amp;iter_info)&amp;#34; call. Each of these calls locks the targets using the &amp;#34;down_read(&amp;amp;_lock)&amp;#34; and &amp;#34;up_read(&amp;amp;_lock)&amp;#34; calls, however between the first and second &amp;#34;dm_target_iterate&amp;#34; there is no lock held and the target modules can be loaded at this point, so the second &amp;#34;dm_target_iterate&amp;#34; call may need more space than what was the first &amp;#34;dm_target_iterate&amp;#34; returned. The code tries to handle this overflow (see the beginning of list_version_get_info), however this handling is incorrect. The code sets &amp;#34;param-&amp;gt;data_size = param-&amp;gt;data_start + needed&amp;#34; and &amp;#34;iter_info.end = (char *)vers+len&amp;#34; - &amp;#34;needed&amp;#34; is the size returned by the first dm_target_iterate call; &amp;#34;len&amp;#34; is the size of the buffer allocated by userspace. &amp;#34;len&amp;#34; may be greater than &amp;#34;needed&amp;#34;; in this case, the code will write up to &amp;#34;len&amp;#34; bytes into the buffer, however param-&amp;gt;data_size is set to &amp;#34;needed&amp;#34;, so it may write data past the param-&amp;gt;data_size value. The ioctl interface copies only up to param-&amp;gt;data_size into userspace, thus part of the result will be truncated. Fix this bug by setting &amp;#34;iter_info.end = (char *)vers + needed;&amp;#34; - this guarantees that the second &amp;#34;dm_target_iterate&amp;#34; call will wri…&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 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm ioctl: fix misbehavior if list_versions races with module loading __list_versions will first estimate the required space using the &amp;#34;dm_target_iterate(list_version_get_needed, &amp;amp;needed)&amp;#34; call and then will fill the space using the &amp;#34;dm_target_iterate(list_version_get_info, &amp;amp;iter_info)&amp;#34; call. Each of these calls locks the targets using the &amp;#34;down_read(&amp;amp;_lock)&amp;#34; and &amp;#34;up_read(&amp;amp;_lock)&amp;#34; calls, however between the first and second &amp;#34;dm_target_iterate&amp;#34; there is no lock held and the target modules can be loaded at this point, so the second &amp;#34;dm_target_iterate&amp;#34; call may need more space than what was the first &amp;#34;dm_target_iterate&amp;#34; returned. The code tries to handle this overflow (see the beginning of list_version_get_info), however this handling is incorrect. The code sets &amp;#34;param-&amp;gt;data_size = param-&amp;gt;data_start + needed&amp;#34; and &amp;#34;iter_info.end = (char *)vers+len&amp;#34; - &amp;#34;needed&amp;#34; is the size returned by the first dm_target_iterate call; &amp;#34;len&amp;#34; is the size of the buffer allocated by userspace. &amp;#34;len&amp;#34; may be greater than &amp;#34;needed&amp;#34;; in this case, the code will write up to &amp;#34;len&amp;#34; bytes into the buffer, however param-&amp;gt;data_size is set to &amp;#34;needed&amp;#34;, so it may write data past the param-&amp;gt;data_size value. The ioctl interface copies only up to param-&amp;gt;data_size into userspace, thus part of the result will be truncated. Fix this bug by setting &amp;#34;iter_info.end = (char *)vers + needed;&amp;#34; - this guarantees that the second &amp;#34;dm_target_iterate&amp;#34; call will wri…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49771</guid>
    </item>
  </channel>
</rss>
