CVE-2026-80975
mfd: qnap-mcu: keep the reply buffer alive past a command timeout
Reported by linux · Published September 11, 2026
In the Linux kernel, the following vulnerability has been resolved: mfd: qnap-mcu: keep the reply buffer alive past a command timeout qnap_mcu_exec() publishes an on-stack buffer to the receive path: unsigned char rx[QNAP_MCU_RX_BUFFER_SIZE]; ... reply->data = rx; reply->length = length; and qnap_mcu_receive_buf() writes into it from the serdev receive path, which runs out of flush_to_ldisc() and is not serialized against qnap_mcu_exec() at all. bus_lock cannot cover it, because qnap_mcu_exec() holds that mutex across wait_for_completion_timeout(). On a timeout qnap_mcu_exec() returns with reply->data still pointing at its own frame. A reply that arrives late, or an unsolicited message from the MCU, is then written into a stack frame that has been left, corrupting whatever runs next on that stack. The same applies when qnap_mcu_write() fails, since that path returns without touching the reply state either. Move the receive buffer into struct qnap_mcu. It is 37 bytes and the structure is devm_kzalloc()ed, so it lives as long as the driver, and a late write lands in memory that is still valid and is reinitialized by the next command. bus_lock keeps commands from sharing it. This deliberately does not clear reply->data or reply->length on the timeout path. Doing so races with qnap_mcu_receive_buf(), which reads both after its if (!reply->length) return size; check: clearing reply->data gives a NULL dereference, and clearing reply->length alone removes the reply->received == reply->length exit condition, so the copy loop runs until the uart chunk is consumed and overruns the buffer. Leaving both set keeps the write bounded by reply->length, which qnap_mcu_exec() has already checked against sizeof(mcu->rx).
EPSS 0.17% · 6.8th percentile
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 998f70d1806bb718a7565f350283e4a79c8cbb4b, 998f70d1806bb718a7565f350283e4a79c8cbb4b, 998f70d1806bb718a7565f350283e4a79c8cbb4b |
| Linux | Linux | 6.14, 0, 6.18.51 |
| linux | linux_kernel | 6.14, 6.14, 6.14 |
| Linux | Linux | 998f70d1806bb718a7565f350283e4a79c8cbb4b, 998f70d1806bb718a7565f350283e4a79c8cbb4b, 998f70d1806bb718a7565f350283e4a79c8cbb4b |
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (12 in total, the first dated here)
- Sep 12, 2026 Coalition ESS Score
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80975
vulnetix vdb fixes CVE-2026-80975
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80975/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart