arm64/module: deal with ambiguity in PRELxx relocation ranges (1cf24a2c) · Commits · 戴 / test

The R_AARCH64_PREL16 and R_AARCH64_PREL32 relocations are documented as permitting a range of [-2^15 .. 2^16), resp. [-2^31 .. 2^32). It is also documented that this means we cannot detect overflow in some cases, which is bad. Since we always interpret the targets of these relocations as signed quantities (e.g., in the ksymtab handling code), let's tighten the overflow checks so that targets that are out of range for our signed interpretation of the relocated quantity get flagged. Signed-off-by:

Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by:

Will Deacon <will.deacon@arm.com>

arch/arm64/kernel/module.c

+14 −2

Original line number	Diff line number	Diff line
		@@ -96,15 +96,27 @@ static int reloc_data(enum aarch64_reloc_op op, void *place, u64 val, int len)
		{
		s64 sval = do_reloc(op, place, val);

		/*
		* The ELF psABI for AArch64 documents the 16-bit and 32-bit place
		* relative relocations as having a range of [-2^15, 2^16) or
		* [-2^31, 2^32), respectively. However, in order to be able to detect
		* overflows reliably, we have to choose whether we interpret such
		* quantities as signed or as unsigned, and stick with it.
		* The way we organize our address space requires a signed
		* interpretation of 32-bit relative references, so let's use that
		* for all R_AARCH64_PRELxx relocations. This means our upper
		* bound for overflow detection should be Sxx_MAX rather than Uxx_MAX.
		*/

		switch (len) {
		case 16:
		(s16 )place = sval;
		if (sval < S16_MIN \|\| sval > U16_MAX)
		if (sval < S16_MIN \|\| sval > S16_MAX)
		return -ERANGE;
		break;
		case 32:
		(s32 )place = sval;
		if (sval < S32_MIN \|\| sval > U32_MAX)
		if (sval < S32_MIN \|\| sval > S32_MAX)
		return -ERANGE;
		break;
		case 64:

Admin message