ntfs: check overflow when iterating ATTR_RECORDs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < b63ddb3ba61e2d3539f87e095c881e552bc45dab| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ntfs: check overflow when iterating ATTR_RECORDs
Kernel iterates over ATTR_RECORDs in mft record in ntfs_attr_find(). Because the ATTR_RECORDs are next to each other, kernel can get the next ATTR_RECORD from end address of current ATTR_RECORD, through current ATTR_RECORD length field.
The problem is that during iteration, when kernel calculates the end address of current ATTR_RECORD, kernel may trigger an integer overflow bug in executing `a = (ATTR_RECORD*)((u8*)a + le32_to_cpu(a->length))`. This may wrap, leading to a forever iteration on 32bit systems.
This patch solves it by adding some checks on calculating end address of current ATTR_RECORD during iteration.
From the CVE record · Linux
The Linux kernel’s NTFS attribute parser can overflow when calculating the end of an ATTR_RECORD. On 32-bit systems, this can cause iteration to continue indefinitely. The input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running the Linux kernel on 32-bit systems should check their kernel version; affected versions are not specified.