ntfs3: Allocate iomap inline_data using alloc_page
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: Allocate iomap inline_data using alloc_page
This fixes a BUG reported in iomap_write_end_inline: iomap_inline_data_valid checks that the inline_data fits within a page. If the inline_data is allocated with kmemdup there's no guarantee that it's page-aligned, so the check sometimes fails. Allocate it with alloc_page to ensure it's page-aligned.
From the CVE record · Linux
In the Linux kernel’s ntfs3 component, inline data allocated with kmemdup may not be page-aligned, causing a check in iomap_write_end_inline to fail and report a BUG. The input does not specify whether an attacker can trigger this, what access would be required, or whether user interaction is needed.
Engineers running the Linux kernel should check their ntfs3 exposure; affected versions are not specified.