<?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 15:40:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93165</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-93165</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-93165</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-372211</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-372211</link>
      <description>EUVD-2026-372211</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-372211</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93165</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-93165</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/chrome: sensorhub: Fix memory overread in ring handler&lt;/p&gt;
&lt;p&gt;`max_response` and `sensor_num` are read from different EC commands:&lt;/p&gt;
&lt;p&gt;- `max_response` is from cros_ec_get_proto_info().
    ec_dev-&amp;gt;max_response = info-&amp;gt;max_response_packet_size -
                                    sizeof(struct ec_host_response);&lt;/p&gt;
&lt;p&gt;- `sensor_num` is from cros_ec_get_sensor_count().
    sensor_num = cros_ec_get_sensor_count(ec);&lt;/p&gt;
&lt;p&gt;With a malfunctioning EC firmware, it is possible that the `msg-&amp;gt;insize`
(i.e., `fifo_info_length` in the context) could be clamped in
cros_ec_cmd_xfer() because `msg-&amp;gt;insize` is greater than `max_response`.&lt;/p&gt;
&lt;p&gt;int fifo_info_length =
            sizeof(struct ec_response_motion_sense_fifo_info) +
            sizeof(u16) * sensorhub-&amp;gt;sensor_num;&lt;/p&gt;
&lt;p&gt;This means the number of read bytes could be less than expected.  As a
result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler()
overreads the `resp-&amp;gt;fifo_info` buffer.&lt;/p&gt;
&lt;p&gt;Check the return value of cros_ec_cmd_xfer_status() and abort if the
number of bytes read does not match the expected length.&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;platform/chrome: sensorhub: Fix memory overread in ring handler&lt;/p&gt;
&lt;p&gt;`max_response` and `sensor_num` are read from different EC commands:&lt;/p&gt;
&lt;p&gt;- `max_response` is from cros_ec_get_proto_info().
    ec_dev-&amp;gt;max_response = info-&amp;gt;max_response_packet_size -
                                    sizeof(struct ec_host_response);&lt;/p&gt;
&lt;p&gt;- `sensor_num` is from cros_ec_get_sensor_count().
    sensor_num = cros_ec_get_sensor_count(ec);&lt;/p&gt;
&lt;p&gt;With a malfunctioning EC firmware, it is possible that the `msg-&amp;gt;insize`
(i.e., `fifo_info_length` in the context) could be clamped in
cros_ec_cmd_xfer() because `msg-&amp;gt;insize` is greater than `max_response`.&lt;/p&gt;
&lt;p&gt;int fifo_info_length =
            sizeof(struct ec_response_motion_sense_fifo_info) +
            sizeof(u16) * sensorhub-&amp;gt;sensor_num;&lt;/p&gt;
&lt;p&gt;This means the number of read bytes could be less than expected.  As a
result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler()
overreads the `resp-&amp;gt;fifo_info` buffer.&lt;/p&gt;
&lt;p&gt;Check the return value of cros_ec_cmd_xfer_status() and abort if the
number of bytes read does not match the expected length.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-93165</guid>
    </item>
    <item>
      <title>GHSA-4wfm-wp45-cw6m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4wfm-wp45-cw6m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/chrome: sensorhub: Fix memory overread in ring handler&lt;/p&gt;
&lt;p&gt;`max_response` and `sensor_num` are read from different EC commands:&lt;/p&gt;
&lt;p&gt;- `max_response` is from cros_ec_get_proto_info().
    ec_dev-&amp;gt;max_response = info-&amp;gt;max_response_packet_size -
                                    sizeof(struct ec_host_response);&lt;/p&gt;
&lt;p&gt;- `sensor_num` is from cros_ec_get_sensor_count().
    sensor_num = cros_ec_get_sensor_count(ec);&lt;/p&gt;
&lt;p&gt;With a malfunctioning EC firmware, it is possible that the `msg-&amp;gt;insize`
(i.e., `fifo_info_length` in the context) could be clamped in
cros_ec_cmd_xfer() because `msg-&amp;gt;insize` is greater than `max_response`.&lt;/p&gt;
&lt;p&gt;int fifo_info_length =
            sizeof(struct ec_response_motion_sense_fifo_info) +
            sizeof(u16) * sensorhub-&amp;gt;sensor_num;&lt;/p&gt;
&lt;p&gt;This means the number of read bytes could be less than expected.  As a
result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler()
overreads the `resp-&amp;gt;fifo_info` buffer.&lt;/p&gt;
&lt;p&gt;Check the return value of cros_ec_cmd_xfer_status() and abort if the
number of bytes read does not match the expected length.&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;platform/chrome: sensorhub: Fix memory overread in ring handler&lt;/p&gt;
&lt;p&gt;`max_response` and `sensor_num` are read from different EC commands:&lt;/p&gt;
&lt;p&gt;- `max_response` is from cros_ec_get_proto_info().
    ec_dev-&amp;gt;max_response = info-&amp;gt;max_response_packet_size -
                                    sizeof(struct ec_host_response);&lt;/p&gt;
&lt;p&gt;- `sensor_num` is from cros_ec_get_sensor_count().
    sensor_num = cros_ec_get_sensor_count(ec);&lt;/p&gt;
&lt;p&gt;With a malfunctioning EC firmware, it is possible that the `msg-&amp;gt;insize`
(i.e., `fifo_info_length` in the context) could be clamped in
cros_ec_cmd_xfer() because `msg-&amp;gt;insize` is greater than `max_response`.&lt;/p&gt;
&lt;p&gt;int fifo_info_length =
            sizeof(struct ec_response_motion_sense_fifo_info) +
            sizeof(u16) * sensorhub-&amp;gt;sensor_num;&lt;/p&gt;
&lt;p&gt;This means the number of read bytes could be less than expected.  As a
result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler()
overreads the `resp-&amp;gt;fifo_info` buffer.&lt;/p&gt;
&lt;p&gt;Check the return value of cros_ec_cmd_xfer_status() and abort if the
number of bytes read does not match the expected length.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4wfm-wp45-cw6m</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93165</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-93165</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Fix memory overread in ring handler `max_response` and `sensor_num` are read from different EC commands: - `max_response` is from cros_ec_get_proto_info().     ec_dev-&amp;gt;max_response = info-&amp;gt;max_response_packet_size -                                     sizeof(struct ec_host_response); - `sensor_num` is from cros_ec_get_sensor_count().     sensor_num = cros_ec_get_sensor_count(ec); With a malfunctioning EC firmware, it is possible that the `msg-&amp;gt;insize` (i.e., `fifo_info_length` in the context) could be clamped in cros_ec_cmd_xfer() because `msg-&amp;gt;insize` is greater than `max_response`.     int fifo_info_length =             sizeof(struct ec_response_motion_sense_fifo_info) +             sizeof(u16) * sensorhub-&amp;gt;sensor_num; This means the number of read bytes could be less than expected.  As a result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler() overreads the `resp-&amp;gt;fifo_info` buffer. Check the return value of cros_ec_cmd_xfer_status() and abort if the number of bytes read does not match the expected length.&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Fix memory overread in ring handler `max_response` and `sensor_num` are read from different EC commands: - `max_response` is from cros_ec_get_proto_info().     ec_dev-&amp;gt;max_response = info-&amp;gt;max_response_packet_size -                                     sizeof(struct ec_host_response); - `sensor_num` is from cros_ec_get_sensor_count().     sensor_num = cros_ec_get_sensor_count(ec); With a malfunctioning EC firmware, it is possible that the `msg-&amp;gt;insize` (i.e., `fifo_info_length` in the context) could be clamped in cros_ec_cmd_xfer() because `msg-&amp;gt;insize` is greater than `max_response`.     int fifo_info_length =             sizeof(struct ec_response_motion_sense_fifo_info) +             sizeof(u16) * sensorhub-&amp;gt;sensor_num; This means the number of read bytes could be less than expected.  As a result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler() overreads the `resp-&amp;gt;fifo_info` buffer. Check the return value of cros_ec_cmd_xfer_status() and abort if the number of bytes read does not match the expected length.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-93165</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3444 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444</guid>
    </item>
  </channel>
</rss>
