https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 10:45:43 +0000 https://vulnerability.circl.lu/vuln/cve-2025-38398 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>spi: spi-qpic-snand: reallocate BAM transactions</p> <p>Using the mtd_nandbiterrs module for testing the driver occasionally results in weird things like below.</p> <p>1. swiotlb mapping fails with the following message:</p> <p>[ 85.926216] qcom_snand 79b0000.spi: swiotlb buffer is full (sz: 4294967294 bytes), total 512 (slots), used 0 (slots) [ 85.932937] qcom_snand 79b0000.spi: failure in mapping desc [ 87.999314] qcom_snand 79b0000.spi: failure to write raw page [ 87.999352] mtd_nandbiterrs: error: write_oob failed (-110)</p> <p>Rebooting the board after this causes a panic due to a NULL pointer dereference.</p> <p>2. If the swiotlb mapping does not fail, rebooting the board may result in a different panic due to a bad spinlock magic:</p> <p>[ 256.104459] BUG: spinlock bad magic on CPU#3, procd/2241 [ 256.104488] Unable to handle kernel paging request at virtual address ffffffff0000049b ...</p> <p>Investigating the issue revealed that these symptoms are results of memory corruption which is caused by out of bounds access within the driver.</p> <p>The driver uses a dynamically allocated structure for BAM transactions, which structure must have enough space for all possible variations of different flash operations initiated by the driver. The required space heavily depends on the actual number of &#39;codewords&#39; which is calculated from the pagesize of the actual NAND chip.</p> <p>Although the qcom_nandc_alloc() function allocates m…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>spi: spi-qpic-snand: reallocate BAM transactions</p> <p>Using the mtd_nandbiterrs module for testing the driver occasionally results in weird things like below.</p> <p>1. swiotlb mapping fails with the following message:</p> <p>[ 85.926216] qcom_snand 79b0000.spi: swiotlb buffer is full (sz: 4294967294 bytes), total 512 (slots), used 0 (slots) [ 85.932937] qcom_snand 79b0000.spi: failure in mapping desc [ 87.999314] qcom_snand 79b0000.spi: failure to write raw page [ 87.999352] mtd_nandbiterrs: error: write_oob failed (-110)</p> <p>Rebooting the board after this causes a panic due to a NULL pointer dereference.</p> <p>2. If the swiotlb mapping does not fail, rebooting the board may result in a different panic due to a bad spinlock magic:</p> <p>[ 256.104459] BUG: spinlock bad magic on CPU#3, procd/2241 [ 256.104488] Unable to handle kernel paging request at virtual address ffffffff0000049b ...</p> <p>Investigating the issue revealed that these symptoms are results of memory corruption which is caused by out of bounds access within the driver.</p> <p>The driver uses a dynamically allocated structure for BAM transactions, which structure must have enough space for all possible variations of different flash operations initiated by the driver. The required space heavily depends on the actual number of &#39;codewords&#39; which is calculated from the pagesize of the actual NAND chip.</p> <p>Although the qcom_nandc_alloc() function allocates m…</p> https://vulnerability.circl.lu/vuln/cve-2025-38398