https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 18:20:00 +0000 https://cve.radiocsirt.org/vuln/cve-2025-38538 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dmaengine: nbpfaxi: Fix memory corruption in probe()</p> <p>The nbpf-&gt;chan[] array is allocated earlier in the nbpf_probe() function and it has &#34;num_channels&#34; elements. These three loops iterate one element farther than they should and corrupt memory.</p> <p>The changes to the second loop are more involved. In this case, we&#39;re copying data from the irqbuf[] array into the nbpf-&gt;chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don&#39;t go beyond the end of the irqbuf[] array. I&#39;m pretty sure this can&#39;t happen, but it seemed harmless to add a check.</p> <p>On the other hand, after the loop has ended there is a check to ensure that the &#34;chan&#34; iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn&#39;t in the correct place and it would always return -EINVAL. However, now it will always be in the correct place. I deleted the check since we know the result.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dmaengine: nbpfaxi: Fix memory corruption in probe()</p> <p>The nbpf-&gt;chan[] array is allocated earlier in the nbpf_probe() function and it has &#34;num_channels&#34; elements. These three loops iterate one element farther than they should and corrupt memory.</p> <p>The changes to the second loop are more involved. In this case, we&#39;re copying data from the irqbuf[] array into the nbpf-&gt;chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don&#39;t go beyond the end of the irqbuf[] array. I&#39;m pretty sure this can&#39;t happen, but it seemed harmless to add a check.</p> <p>On the other hand, after the loop has ended there is a check to ensure that the &#34;chan&#34; iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn&#39;t in the correct place and it would always return -EINVAL. However, now it will always be in the correct place. I deleted the check since we know the result.</p> https://cve.radiocsirt.org/vuln/cve-2025-38538