{"id":12354,"date":"2026-09-04T18:54:18","date_gmt":"2026-09-04T10:54:18","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-80712"},"modified":"2026-09-04T18:54:18","modified_gmt":"2026-09-04T10:54:18","slug":"cve-2026-80712","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-80712","title":{"rendered":"CVE-2026-80712 [HIGH] &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nspi: spi-qpic-snand:"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>spi: spi-qpic-snand: write the feature value before executing SET_FEATURE<\/p>\n<p>qcom_spi_send_cmdaddr() programs NAND_FLASH_CMD\/NAND_EXEC_CMD and submits<br \/>\nthe descriptors, which makes the controller execute the command<br \/>\nimmediately. For SPINAND_SET_FEATURE the value to be written is only<br \/>\nplaced into NAND_FLASH_FEATURES afterwards, by qcom_spi_io_op(), in a<br \/>\nsecond submission &#8211; so the chip is programmed with whatever that register<br \/>\nhappened to hold from a previous operation, and the intended value is only<br \/>\napplied by the *next* SET_FEATURE.<\/p>\n<p>Measured on a TP-Link Archer AX55 v1 (IPQ5018, ESMT F50L1G41LB): writing<br \/>\n0x40 to the configuration register (0xb0) leaves the chip at 0x00, and the<br \/>\nsubsequent write of 0x00 leaves it at 0x40 &#8211; every write lands one<br \/>\noperation late.<\/p>\n<p>This stayed unnoticed until v6.18 added SPI-NAND OTP support together<br \/>\nwith OTP entries for ESMT chips. spinand_otp_rw() enables OTP mode,<br \/>\nreads, and disables it again, and mtd_otp_nvmem_add() does this during<br \/>\nMTD registration. With the off-by-one, the &#8220;disable&#8221; write actually<br \/>\napplies the previously requested value, so CFG_OTP_ENABLE ends up set:<br \/>\nthe chip stays in OTP mode, every subsequent array read returns the OTP<br \/>\narea instead of the array (UBI reports an empty device) and all writes<br \/>\nfail with -EIO because the OTP area is write protected. On this board<br \/>\nthat makes the whole flash unusable and the device unbootable.<\/p>\n<p>Write the feature value into NAND_FLASH_FEATURES as part of the same<br \/>\ntransaction, before NAND_EXEC_CMD. While at it, copy only the bytes the<br \/>\noperation actually carries &#8211; the previous code dereferenced a 4-byte<br \/>\npointer on a one-byte buffer (spinand-&gt;scratchbuf).<\/p>\n<p>With this patch the flash contents read back bit-identical to a<br \/>\nknown-good dump of the same board taken under the vendor firmware<br \/>\n(md5-verified across partitions), and writes work.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>spi: spi-qpic-snand: write the feature value before executing SET_FEATURE<\/p>\n<p>qcom_spi_send_cmdaddr() programs NAND_FLASH_CMD\/NAND_EXE<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-12354","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/12354","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12354"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12354"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12354"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}