regmap: maple: Fix cache corruption in regcache_maple_drop()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.266.8.56.9In the Linux kernel, the following vulnerability has been resolved:
regmap: maple: Fix cache corruption in regcache_maple_drop()
When keeping the upper end of a cache block entry, the entry[] array must be indexed by the offset from the base register of the block, i.e. max - mas.index.
The code was indexing entry[] by only the register address, leading to an out-of-bounds access that copied some part of the kernel memory over the cache contents.
This bug was not detected by the regmap KUnit test because it only tests with a block of registers starting at 0, so mas.index == 0.
From the CVE record · Linux
The Linux kernel’s regmap maple cache can read out of bounds when dropping part of a cache block whose base register is not zero. This can copy kernel memory into the cache and corrupt its contents. The input does not establish an attacker path or whether access, authentication, or user interaction is required.
Engineers running the Linux kernel should check whether their kernel includes the affected regmap maple code; affected versions were not provided.