<?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://127.0.0.1:10001</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, 21 Nov 2026 01:43:08 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-22003</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-22003</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://127.0.0.1:10001/vuln/bell-cve-2025-22003</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0449 — 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://127.0.0.1:10001/vuln/certfr-2025-avi-0449</link>
      <description>certfr-2025-avi-0449</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0449</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-22003</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22003</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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: ucan: fix out of bound read in strscpy() source Commit 7fdaf8966aae (&amp;#34;can: ucan: use strscpy() to instead of strncpy()&amp;#34;) unintentionally introduced a one byte out of bound read on strscpy()&amp;#39;s source argument (which is kind of ironic knowing that strscpy() is meant to be a more secure alternative :)). Let&amp;#39;s consider below buffers:   dest[len + 1]; /* will be NUL terminated */   src[len]; /* may not be NUL terminated */ When doing:   strncpy(dest, src, len);   dest[len] = &amp;#39;\0&amp;#39;; strncpy() will read up to len bytes from src. On the other hand:   strscpy(dest, src, len + 1); will read up to len + 1 bytes from src, that is to say, an out of bound read of one byte will occur on src if it is not NUL terminated. Note that the src[len] byte is never copied, but strscpy() still needs to read it to check whether a truncation occurred or not. This exact pattern happened in ucan. The root cause is that the source is not NUL terminated. Instead of doing a copy in a local buffer, directly NUL terminate it as soon as usb_control_msg() returns. With this, the local firmware_str[] variable can be removed. On top of this do a couple refactors:   - ucan_ctl_payload-&amp;gt;raw is only used for the firmware string, so     rename it to ucan_ctl_payload-&amp;gt;fw_str and change its type from u8 to     char.   - ucan_device_request_in() is only used to retrieve the firmware     string, so rename it to ucan_get_fw_str() and refactor it to ma…&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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: ucan: fix out of bound read in strscpy() source Commit 7fdaf8966aae (&amp;#34;can: ucan: use strscpy() to instead of strncpy()&amp;#34;) unintentionally introduced a one byte out of bound read on strscpy()&amp;#39;s source argument (which is kind of ironic knowing that strscpy() is meant to be a more secure alternative :)). Let&amp;#39;s consider below buffers:   dest[len + 1]; /* will be NUL terminated */   src[len]; /* may not be NUL terminated */ When doing:   strncpy(dest, src, len);   dest[len] = &amp;#39;\0&amp;#39;; strncpy() will read up to len bytes from src. On the other hand:   strscpy(dest, src, len + 1); will read up to len + 1 bytes from src, that is to say, an out of bound read of one byte will occur on src if it is not NUL terminated. Note that the src[len] byte is never copied, but strscpy() still needs to read it to check whether a truncation occurred or not. This exact pattern happened in ucan. The root cause is that the source is not NUL terminated. Instead of doing a copy in a local buffer, directly NUL terminate it as soon as usb_control_msg() returns. With this, the local firmware_str[] variable can be removed. On top of this do a couple refactors:   - ucan_ctl_payload-&amp;gt;raw is only used for the firmware string, so     rename it to ucan_ctl_payload-&amp;gt;fw_str and change its type from u8 to     char.   - ucan_device_request_in() is only used to retrieve the firmware     string, so rename it to ucan_get_fw_str() and refactor it to ma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22003</guid>
    </item>
  </channel>
</rss>
