btrfs: fix extent map leak in NOCOW direct I/O write
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5f9a8a51d8b95505d8de8b7191ae2ed8c504d4af · < 3f950867c307c5413d628a153ac44915bd117ffd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix extent map leak in NOCOW direct I/O write
btrfs_dio_iomap_begin() calls btrfs_get_extent(), which returns an extent map reference that must be dropped on all exit paths.
For direct writes into a NOCOW range, btrfs_get_blocks_direct_write() keeps using that extent map and asks btrfs_create_dio_extent() to allocate the ordered extent. If that fails, for example because btrfs_alloc_ordered_extent() fails, the function returns the error without dropping the input extent map. The PREALLOC path avoided this by dropping the input extent map before replacing it with the newly created one.
Check the error from btrfs_create_dio_extent() before replacing the map and drop the input extent map on failure.
From the CVE record · Linux
The Linux kernel's btrfs code can leak an extent map reference when allocation fails during a direct write to a NOCOW range. The input does not describe an attacker action or specify whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with btrfs should check their versions; affected versions are not specified.