{
  "id": "CVE-2026-80712",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-80712",
  "published_at": "2026-08-28T06:53:11.243Z",
  "title": "spi: spi-qpic-snand: write the feature value before executing SET_FEATURE",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 8.4,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: spi-qpic-snand: write the feature value before executing SET_FEATURE\n\nqcom_spi_send_cmdaddr() programs NAND_FLASH_CMD/NAND_EXEC_CMD and submits\nthe descriptors, which makes the controller execute the command\nimmediately. For SPINAND_SET_FEATURE the value to be written is only\nplaced into NAND_FLASH_FEATURES afterwards, by qcom_spi_io_op(), in a\nsecond submission - so the chip is programmed with whatever that register\nhappened to hold from a previous operation, and the intended value is only\napplied by the *next* SET_FEATURE.\n\nMeasured on a TP-Link Archer AX55 v1 (IPQ5018, ESMT F50L1G41LB): writing\n0x40 to the configuration register (0xb0) leaves the chip at 0x00, and the\nsubsequent write of 0x00 leaves it at 0x40 - every write lands one\noperation late.\n\nThis stayed unnoticed until v6.18 added SPI-NAND OTP support together\nwith OTP entries for ESMT chips. spinand_otp_rw() enables OTP mode,\nreads, and disables it again, and mtd_otp_nvmem_add() does this during\nMTD registration. With the off-by-one, the \"disable\" write actually\napplies the previously requested value, so CFG_OTP_ENABLE ends up set:\nthe chip stays in OTP mode, every subsequent array read returns the OTP\narea instead of the array (UBI reports an empty device) and all writes\nfail with -EIO because the OTP area is write protected. On this board\nthat makes the whole flash unusable and the device unbootable.\n\nWrite the feature value into NAND_FLASH_FEATURES as part of the same\ntransaction, before NAND_EXEC_CMD. While at it, copy only the bytes the\noperation actually carries - the previous code dereferenced a 4-byte\npointer on a one-byte buffer (spinand-\u003escratchbuf).\n\nWith this patch the flash contents read back bit-identical to a\nknown-good dump of the same board taken under the vendor firmware\n(md5-verified across partitions), and writes work.",
  "cvss_by_source": {
    "cna": 8.4
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 7304d1909080ef0c9da703500a97f46c98393fcd, \u003c 581e5166f0780103dc91c0d8ebc801f9af4824b0",
          "\u003e= 7304d1909080ef0c9da703500a97f46c98393fcd, \u003c 3ba021079ef2ac6e21e3547328496ac42d22b56a",
          "\u003e= 7304d1909080ef0c9da703500a97f46c98393fcd, \u003c 8fd62901d6bf03f274a49dd0060793cc07dd51b0"
        ],
        "fixed_in": [
          "581e5166f0780103dc91c0d8ebc801f9af4824b0",
          "3ba021079ef2ac6e21e3547328496ac42d22b56a",
          "8fd62901d6bf03f274a49dd0060793cc07dd51b0"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.15"
        ],
        "fixed_in": [
          "0",
          "6.18.44",
          "7.1.8",
          "7.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 581e5166f0780103dc91c0d8ebc801f9af4824b0 or 3ba021079ef2ac6e21e3547328496ac42d22b56a or 8fd62901d6bf03f274a49dd0060793cc07dd51b0 or later.",
      "Upgrade Linux to 0 or 6.18.44 or 7.1.8 or 7.2 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
