<?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://vulnerability.circl.lu</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 14:36:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23092 — iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23092</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source&lt;/p&gt;
&lt;p&gt;When simple_write_to_buffer() succeeds, it returns the number of bytes
actually copied to the buffer. The code incorrectly uses &amp;#39;count&amp;#39;
as the index for null termination instead of the actual bytes copied.
If count exceeds the buffer size, this leads to out-of-bounds write.
Add a check for the count and use the return value as the index.&lt;/p&gt;
&lt;p&gt;The bug was validated using a demo module that mirrors the original
code and was tested under QEMU.&lt;/p&gt;
&lt;p&gt;Pattern of the bug:
- A fixed 64-byte stack buffer is filled using count.
- If count &amp;gt; 64, the code still does buf[count] = &amp;#39;\0&amp;#39;, causing an
- out-of-bounds write on the stack.&lt;/p&gt;
&lt;p&gt;Steps for reproduce:
- Opens the device node.
- Writes 128 bytes of A to it.
- This overflows the 64-byte stack buffer and KASAN reports the OOB.&lt;/p&gt;
&lt;p&gt;Found via static analysis. This is similar to the
commit da9374819eb3 (&amp;#34;iio: backend: fix out-of-bound write&amp;#34;)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source&lt;/p&gt;
&lt;p&gt;When simple_write_to_buffer() succeeds, it returns the number of bytes
actually copied to the buffer. The code incorrectly uses &amp;#39;count&amp;#39;
as the index for null termination instead of the actual bytes copied.
If count exceeds the buffer size, this leads to out-of-bounds write.
Add a check for the count and use the return value as the index.&lt;/p&gt;
&lt;p&gt;The bug was validated using a demo module that mirrors the original
code and was tested under QEMU.&lt;/p&gt;
&lt;p&gt;Pattern of the bug:
- A fixed 64-byte stack buffer is filled using count.
- If count &amp;gt; 64, the code still does buf[count] = &amp;#39;\0&amp;#39;, causing an
- out-of-bounds write on the stack.&lt;/p&gt;
&lt;p&gt;Steps for reproduce:
- Opens the device node.
- Writes 128 bytes of A to it.
- This overflows the 64-byte stack buffer and KASAN reports the OOB.&lt;/p&gt;
&lt;p&gt;Found via static analysis. This is similar to the
commit da9374819eb3 (&amp;#34;iio: backend: fix out-of-bound write&amp;#34;)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23092</guid>
    </item>
  </channel>
</rss>
