ext4: use memtostr_pad() for s_volume_name
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:
ext4: use memtostr_pad() for s_volume_name
As with the other strings in struct ext4_super_block, s_volume_name is not NUL terminated. The other strings were marked in commit 072ebb3bffe6 ("ext4: add nonstring annotations to ext4.h"). Using strscpy() isn't the right replacement for strncpy(); it should use memtostr_pad() instead.
From the CVE record · Linux
The Linux kernel's ext4 code uses strscpy() for s_volume_name, a field that is not NUL-terminated; the fix uses memtostr_pad() instead. The input does not specify what an attacker could do, what access they would need, or whether user interaction is required.
Engineers running Linux systems that use ext4 should check their kernel versions; affected versions are not specified.