ethtool: cmis: validate start_cmd_payload_size from module
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ethtool: cmis: validate start_cmd_payload_size from module
The CMIS firmware update code reads start_cmd_payload_size from the module's FW Management Features CDB reply and uses it directly as the byte count for memcpy. The destination buffer is 112 bytes (ETHTOOL_CMIS_CDB_LPL_MAX_PL_LENGTH - 8). So a malicious module (or corrupted response) can cause a OOB write later on in cmis_fw_update_start_download().
Let's error out. If modules that expect longer LPL writes actually exist we should revisit.
struct cmis_cdb_start_fw_download_pl's definition has to move, no change there.
From the CVE record · Linux
The Linux kernel's ethtool CMIS firmware update code uses a module-provided payload size without checking it against a 112-byte destination buffer. A malicious module or corrupted response can cause an out-of-bounds write during firmware download; the input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel with ethtool CMIS firmware update support should check their deployments; affected versions are not specified.