dm era: fix out-of-bounds memory access for non-zero start sector
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ eec40579d84873dfb7021eb24c50360f073237c5 · < 1fcb5e29dd7a5b85adb9d8b539911741d878e829| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dm era: fix out-of-bounds memory access for non-zero start sector
dm-era tracks writes in target-relative blocks, but era_map() calculates the writeset block before applying the target offset. Tables with a non-zero start sector can therefore pass an absolute mapped-device block to metadata_current_marked().
If the absolute block is beyond the current writeset size, writeset_marked() tests past the end of the in-core bitset. KASAN reports this as a vmalloc-out-of-bounds access.
Apply the target offset before calculating the era block so writeset lookups use the target-relative block number.
From the CVE record · Linux
The Linux kernel's dm-era target can read past an in-memory bitset when a device-mapper table uses a non-zero start sector and the resulting block is beyond the current writeset. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with dm-era tables that use a non-zero start sector should check their installations; affected versions are not specified.