ntfs3: fix integer overflow in run_unpack() volume boundary check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82cae269cfa953032fbb8980a7d554d60fb00b17 · < 6175d09c23bec4b60860ee9a0170308ff4b56e10| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: fix integer overflow in run_unpack() volume boundary check
The volume boundary check `lcn + len > sbi->used.bitmap.nbits` uses raw addition which can wrap around for large lcn and len values, bypassing the validation. Use check_add_overflow() as is already done for the adjacent prev_lcn + dlcn and vcn64 + len checks added by commit 3ac37e100385 ("ntfs3: Fix integer overflow in run_unpack()").
Found by fuzzing with a source-patched harness (LibAFL + QEMU).
From the CVE record · Linux
The ntfs3 run_unpack() volume boundary check can overflow when adding large lcn and len values. This can let those values bypass validation; the input does not specify an attack route, authentication requirements, or user interaction.
Engineers running Linux kernels with ntfs3 should check their versions; affected versions are not specified.