udf: Fix uninitialized array access for some pathnames
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 484a10f49387e4386bf2708532e75bf78ffea2cb · < a6824149809395dfbb5bc36bc7057cc3cb84e56d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
udf: Fix uninitialized array access for some pathnames
For filenames that begin with . and are between 2 and 5 characters long, UDF charset conversion code would read uninitialized memory in the output buffer. The only practical impact is that the name may be prepended a "unification hash" when it is not actually needed but still it is good to fix this.
From the CVE record · Linux
The Linux kernel's UDF charset conversion code can read uninitialized output-buffer memory when a filename begins with a dot and is 2–5 characters long. The practical impact is that the filename may receive an unnecessary “unification hash.” The input does not specify an attacker access requirement or user-interaction condition.
Engineers running Linux kernels that use UDF should check their kernel version; affected versions are not specified.