<?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>Sun, 04 Oct 2026 06:02:03 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10712</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10712</link>
      <description>bdu:2026-10712</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10712</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-31624</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-31624</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-31624</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0526 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0526</link>
      <description>certfr-2026-avi-0526</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0526</guid>
    </item>
    <item>
      <title>EUVD-2026-327038</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327038</link>
      <description>EUVD-2026-327038</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327038</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31624</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31624</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: core: clamp report_size in s32ton() to avoid undefined shift&lt;/p&gt;
&lt;p&gt;s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that
comes directly from a HID device.  The HID parser bounds report_size
only to &amp;lt;= 256, so a broken HID device can supply a report descriptor
with a wide field that triggers shift exponents up to 256 on a 32-bit
type when an output report is built via hid_output_field() or
hid_set_field().&lt;/p&gt;
&lt;p&gt;Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in
hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function
snto32(), but s32ton() was never given the same fix as I guess syzbot
hadn&amp;#39;t figured out how to fuzz a device the same way.&lt;/p&gt;
&lt;p&gt;Fix this up by just clamping the max value of n, just like snto32()
does.&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: core: clamp report_size in s32ton() to avoid undefined shift&lt;/p&gt;
&lt;p&gt;s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that
comes directly from a HID device.  The HID parser bounds report_size
only to &amp;lt;= 256, so a broken HID device can supply a report descriptor
with a wide field that triggers shift exponents up to 256 on a 32-bit
type when an output report is built via hid_output_field() or
hid_set_field().&lt;/p&gt;
&lt;p&gt;Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in
hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function
snto32(), but s32ton() was never given the same fix as I guess syzbot
hadn&amp;#39;t figured out how to fuzz a device the same way.&lt;/p&gt;
&lt;p&gt;Fix this up by just clamping the max value of n, just like snto32()
does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31624</guid>
    </item>
    <item>
      <title>GHSA-7r46-pv4v-9gxj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7r46-pv4v-9gxj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: core: clamp report_size in s32ton() to avoid undefined shift&lt;/p&gt;
&lt;p&gt;s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that
comes directly from a HID device.  The HID parser bounds report_size
only to &amp;lt;= 256, so a broken HID device can supply a report descriptor
with a wide field that triggers shift exponents up to 256 on a 32-bit
type when an output report is built via hid_output_field() or
hid_set_field().&lt;/p&gt;
&lt;p&gt;Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in
hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function
snto32(), but s32ton() was never given the same fix as I guess syzbot
hadn&amp;#39;t figured out how to fuzz a device the same way.&lt;/p&gt;
&lt;p&gt;Fix this up by just clamping the max value of n, just like snto32()
does.&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: core: clamp report_size in s32ton() to avoid undefined shift&lt;/p&gt;
&lt;p&gt;s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that
comes directly from a HID device.  The HID parser bounds report_size
only to &amp;lt;= 256, so a broken HID device can supply a report descriptor
with a wide field that triggers shift exponents up to 256 on a 32-bit
type when an output report is built via hid_output_field() or
hid_set_field().&lt;/p&gt;
&lt;p&gt;Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in
hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function
snto32(), but s32ton() was never given the same fix as I guess syzbot
hadn&amp;#39;t figured out how to fuzz a device the same way.&lt;/p&gt;
&lt;p&gt;Fix this up by just clamping the max value of n, just like snto32()
does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7r46-pv4v-9gxj</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-31624 — HID: core: clamp report_size in s32ton() to avoid undefined shift</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-31624</link>
      <description>msrc_CVE-2026-31624</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-31624</guid>
    </item>
    <item>
      <title>OESA-2026-2312 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2312</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc()&lt;/p&gt;
&lt;p&gt;At the end of this function, d is the traversal cursor of flist, but the
code completes found instead. This can lead to issues such as NULL pointer
dereferences, double completion, or descriptor leaks.&lt;/p&gt;
&lt;p&gt;Fix this by completing d instead of found in the final
list_for_each_entry_safe() loop.(CVE-2026-31436)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hwmon: (pmbus/core) Protect regulator operations with mutex&lt;/p&gt;
&lt;p&gt;The regulator operations pmbus_regulator_get_voltage(),
pmbus_regulator_set_voltage(), and pmbus_regulator_list_voltage()
access PMBus registers and shared data but were not protected by
the update_lock mutex. This could lead to race conditions.&lt;/p&gt;
&lt;p&gt;However, adding mutex protection directly to these functions causes
a deadlock because pmbus_regulator_notify() (which calls
regulator_notifier_call_chain()) is often called with the mutex
already held (e.g., from pmbus_fault_handler()). If a regulator
callback then calls one of the now-protected voltage functions,
it will attempt to acquire the same mutex.&lt;/p&gt;
&lt;p&gt;Rework pmbus_regulator_notify() to utilize a worker function to
send notifications outside of the mutex protection. Events are
stored as atomics in a per-page bitmask and processed by the worker.&lt;/p&gt;
&lt;p&gt;Initialize the worker and its as…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc()&lt;/p&gt;
&lt;p&gt;At the end of this function, d is the traversal cursor of flist, but the
code completes found instead. This can lead to issues such as NULL pointer
dereferences, double completion, or descriptor leaks.&lt;/p&gt;
&lt;p&gt;Fix this by completing d instead of found in the final
list_for_each_entry_safe() loop.(CVE-2026-31436)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;hwmon: (pmbus/core) Protect regulator operations with mutex&lt;/p&gt;
&lt;p&gt;The regulator operations pmbus_regulator_get_voltage(),
pmbus_regulator_set_voltage(), and pmbus_regulator_list_voltage()
access PMBus registers and shared data but were not protected by
the update_lock mutex. This could lead to race conditions.&lt;/p&gt;
&lt;p&gt;However, adding mutex protection directly to these functions causes
a deadlock because pmbus_regulator_notify() (which calls
regulator_notifier_call_chain()) is often called with the mutex
already held (e.g., from pmbus_fault_handler()). If a regulator
callback then calls one of the now-protected voltage functions,
it will attempt to acquire the same mutex.&lt;/p&gt;
&lt;p&gt;Rework pmbus_regulator_notify() to utilize a worker function to
send notifications outside of the mutex protection. Events are
stored as atomics in a per-page bitmask and processed by the worker.&lt;/p&gt;
&lt;p&gt;Initialize the worker and its as…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2312</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10703-1 — kernel-devel-7.0.3-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10703-1</link>
      <description>&lt;p&gt;kernel-devel-7.0.3-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.0.3-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10703-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31624</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31624</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 244 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: core: clamp report_size in s32ton() to avoid undefined shift s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that comes directly from a HID device.  The HID parser bounds report_size only to &amp;lt;= 256, so a broken HID device can supply a report descriptor with a wide field that triggers shift exponents up to 256 on a 32-bit type when an output report is built via hid_output_field() or hid_set_field(). Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function snto32(), but s32ton() was never given the same fix as I guess syzbot hadn&amp;#39;t figured out how to fuzz a device the same way. Fix this up by just clamping the max value of n, just like snto32() does.&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 244 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: core: clamp report_size in s32ton() to avoid undefined shift s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that comes directly from a HID device.  The HID parser bounds report_size only to &amp;lt;= 256, so a broken HID device can supply a report descriptor with a wide field that triggers shift exponents up to 256 on a 32-bit type when an output report is built via hid_output_field() or hid_set_field(). Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function snto32(), but s32ton() was never given the same fix as I guess syzbot hadn&amp;#39;t figured out how to fuzz a device the same way. Fix this up by just clamping the max value of n, just like snto32() does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31624</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1279 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279</guid>
    </item>
  </channel>
</rss>
