parport: Proper fix for array out-of-bounds access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b579ea3516c371ecf59d073772bc45dfd28c8a0e · < 66029078fee00646e2e9dbb8f41ff7819f8e7569| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
parport: Proper fix for array out-of-bounds access
The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.
Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.
From the CVE record · Linux
The Linux kernel’s parport component has a potential array out-of-bounds access because snprintf() can report a length greater than the number of characters it actually wrote. An attacker may be able to trigger the access, but the input does not specify whether this requires local or network access, authentication, or user interaction.
Anyone running the Linux kernel should check whether their version is affected; affected versions are not specified in the input.