can: softing: fw_parse(): validate firmware record spans
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c · < 2ee477e541a6d5e434d6a4041c6b677ab42e1d82| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: softing: fw_parse(): validate firmware record spans
fw_parse() reads a fixed record header, a firmware-provided payload, and a trailing checksum without knowing the end of the firmware blob. A truncated record can therefore make those reads exceed the blob.
The same record also supplies addresses and lengths for writes into DPRAM. The generic loader uses wrap-prone mixed signed arithmetic for its bounds check, while the application loader does not bound the staging copy at all.
Pass the firmware end to the parser and validate the full source record. Use a signed wide offset for generic DPRAM records and validate the application staging span against the mapped DPRAM before copying.
From the CVE record · Linux
The Linux kernel’s softing CAN firmware parser can read beyond a truncated firmware blob and mishandle bounds on writes to DPRAM. An attacker’s ability to trigger this issue, including required access or user interaction, is not specified in the input.
Engineers running Linux kernels with the softing CAN driver should check their versions; affected versions are not specified.