mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0)
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7b6efc2bc4f19952b25ebf9b236e5ac43cd386c2 · < a04cb99c5d4668fe3f5c0e5b6da1cecd34c3f219| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0)
If an mremap() syscall with old_size=0 ends up in move_page_tables(), it will call invalidate_range_start()/invalidate_range_end() unnecessarily, i.e. with an empty range.
This causes a WARN in KVM's mmu_notifier. In the past, empty ranges have been diagnosed to be off-by-one bugs, hence the WARNing. Given the low (so far) number of unique reports, the benefits of detecting more buggy callers seem to outweigh the cost of having to fix cases such as this one, where userspace is doing something silly. In this particular case, an early return from move_page_tables() is enough to fix the issue.
From the CVE record · Linux
The Linux kernel can unnecessarily send an empty invalidation range to KVM’s mmu_notifier when a local process calls mremap() with old_size=0 and reaches move_page_tables(). This triggers a kernel WARN; the input does not specify whether authentication or further user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified.