lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 7d658da725ea81c91f73087547b97e7ced82d62b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen()
Patch series "lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen()", v2.
This series fixes an off-by-one out-of-bounds read in ucs2_strnlen().
The first patch is the real fix, the second patch comes as a bonus and fixes the code indentation.
This patch (of 2):
ucs2_strnlen() checks the current character before checking whether the caller-provided maximum length has been reached. If the input is not NUL-terminated within that bound, the loop can read one ucs2_char_t past the limit.
Test the length before dereferencing to prevent an off-by-one out-of-bounds read.
From the CVE record · Linux
The Linux kernel's ucs2_strnlen() can read one character past the caller-provided limit when the input is not NUL-terminated within that limit. The input does not specify whether an attacker can trigger this behavior or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified in the input.