Input: synaptics-rmi4 - zero report size on F54 work error
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - zero report size on F54 work error In rmi_f54_work(), if an error occurs during report request or command verification, the code jumped directly to the 'error' label, bypassing the 'abort' label where f54->report_size was normally zeroed out. This left f54->report_size containing its previous successful payload size. If a user then altered the V4L2 format to a smaller size, and a subsequent run failed, rmi_f54_buffer_queue() would copy the stale, larger payload size into the shrunken V4L2 buffer, causing a heap buffer overflow. Fix this by merging the 'abort' and 'error' labels into a single 'out' exit path, and ensuring that f54->report_size is always set to 0 on failure by checking for error and zeroing the local report_size first.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.266, 5.15.217, 6.1.184, 6.12.105, 6.18.46, 6.6.153, 7.1.10
- CVEs
- CVE-2026-80570
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 22:57 UTC · Revision 1
Source evidence
Input: synaptics-rmi4 - zero report size on F54 work error
core-osv · Original sourcePublished 26 Aug 2026, 14:37 UTC
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - zero report size on F54 work error In rmi_f54_work(), if an error occurs during report request or command verification, the code jumped directly to the 'error' label, bypassing the 'abort' label where f54->report_size was normally zeroed out. This left f54->report_size containing its previous successful payload size. If a user then altered the V4L2 format to a smaller size, and a subsequent run failed, rmi_f54_buffer_queue() would copy the stale, larger payload size into the shrunken V4L2 buffer, causing a heap buffer overflow. Fix this by merging the 'abort' and 'error' labels into a single 'out' exit path, and ensuring that f54->report_size is always set to 0 on failure by checking for error and zeroing the local report_size first.
osv:CVE-2026-80570
Kernel
Fixed versions: 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10
Complete source record
{
"id": "f3a5986bf7d7dac7cb3742114c9d9be405f63901b97d4febe610674f7bd50efb",
"url": "https://osv.dev/vulnerability/CVE-2026-80570",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Input: synaptics-rmi4 - zero report size on F54 work error",
"summary": "In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - zero report size on F54 work error In rmi_f54_work(), if an error occurs during report request or command verification, the code jumped directly to the 'error' label, bypassing the 'abort' label where f54->report_size was normally zeroed out. This left f54->report_size containing its previous successful payload size. If a user then altered the V4L2 format to a smaller size, and a subsequent run failed, rmi_f54_buffer_queue() would copy the stale, larger payload size into the shrunken V4L2 buffer, causing a heap buffer overflow. Fix this by merging the 'abort' and 'error' labels into a single 'out' exit path, and ensuring that f54->report_size is always set to 0 on failure by checking for error and zeroing the local report_size first.",
"evidence": "osv:CVE-2026-80570",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.266",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.217",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.184",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.153",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.105",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.46",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-80570",
"aliases": [
"CVE-2026-80570"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3a762dbd5347514c3cb2ac756a92a3d1c7646a2d"
},
{
"fixed": "62079c17ec07d64362bec367ee7a525b0dbf6bf9"
},
{
"fixed": "79521ed3cc9ea48476666ccacf45ecd6954b29a4"
},
{
"fixed": "c669c64ab71afa7b467c4d7e18f6a05e96b97a1f"
},
{
"fixed": "77749685e55da19b187df215b5da4080842ca5c7"
},
{
"fixed": "c6cfda79f26c69e97db9805808c3b44d02227b4b"
},
{
"fixed": "b28593a05afdd812b590e1045b5bd862a5869225"
},
{
"fixed": "88c8174d72900d77fbdf2f527d54b6ff2da876a8"
},
{
"fixed": "dc76c3c8e8ad09362b8c1561f3928288c15cba2e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80570.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.9.0"
},
{
"fixed": "5.10.266"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.217"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.184"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.153"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.105"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.46"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80570.json"
}
}
],
"modified": "2026-10-28T02:30:40.159070063Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/62079c17ec07d64362bec367ee7a525b0dbf6bf9",
"https://git.kernel.org/stable/c/77749685e55da19b187df215b5da4080842ca5c7",
"https://git.kernel.org/stable/c/79521ed3cc9ea48476666ccacf45ecd6954b29a4",
"https://git.kernel.org/stable/c/88c8174d72900d77fbdf2f527d54b6ff2da876a8",
"https://git.kernel.org/stable/c/b28593a05afdd812b590e1045b5bd862a5869225",
"https://git.kernel.org/stable/c/c669c64ab71afa7b467c4d7e18f6a05e96b97a1f",
"https://git.kernel.org/stable/c/c6cfda79f26c69e97db9805808c3b44d02227b4b",
"https://git.kernel.org/stable/c/dc76c3c8e8ad09362b8c1561f3928288c15cba2e",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80570.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-80570",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80570.json"
}
},
"related_cves": [
{
"value": "CVE-2026-80570",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507781,
"published_at": "2026-08-26T14:37:31.94+00:00"
}