udf: Avoid using corrupted block bitmap buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1e0d4adf17e7ef03281d7b16555e7c1508c8ed2d · < 8ca170c39eca7cad6e0cfeb24e351d8f8eddcd65| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
udf: Avoid using corrupted block bitmap buffer
When the filesystem block bitmap is corrupted, we detect the corruption while loading the bitmap and fail the allocation with error. However the next allocation from the same bitmap will notice the bitmap buffer is already loaded and tries to allocate from the bitmap with mixed results (depending on the exact nature of the bitmap corruption). Fix the problem by using BH_verified bit to indicate whether the bitmap is valid or not.
From the CVE record · Linux
The Linux kernel's UDF filesystem can reuse a corrupted block bitmap buffer after detecting corruption and failing an allocation. A subsequent allocation from the same bitmap may then use the invalid buffer, with results depending on the corruption. The input does not specify an attack route, authentication requirements, or user interaction.
Engineers running Linux kernels with UDF filesystem support should check their versions; affected versions are not specified.