video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 9ff2f7294ab0f011cd4d1b7dcd9a07d8fdf72834| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow
Coverity complains of a possible buffer overflow. However, given the 'static' scope of nvidia_setup_i2c_bus() it looks like that can't happen after examiniing the call sites.
CID 19036 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW) 1. fixed_size_dest: You might overrun the 48-character fixed-size string chan->adapter.name by copying name without checking the length. 2. parameter_as_source: Note: This defect has an elevated risk because the source argument is a parameter of the current function. 89 strcpy(chan->adapter.name, name);
Fix this warning by using strscpy() which will silence the warning and prevent any future buffer overflows should the names used to identify the channel become much longer.
From the CVE record · Linux
The Linux kernel’s nvidiafb driver copied a channel name into a fixed-size buffer without checking its length. The reported call sites do not appear to allow an overflow, but longer names could cause one in the future; the input does not establish an attack path or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the nvidiafb driver should check whether their kernel includes the fix; affected versions are not specified.