CVE-2022-50093

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE)<br /> <br /> KASAN reports:<br /> <br /> [ 4.668325][ T0] BUG: KASAN: wild-memory-access in dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/asm/bitops.h:226 include/asm-generic/bitops/instrumented-non-atomic.h:142 include/linux/nodemask.h:415 drivers/iommu/intel/dmar.c:497)<br /> [ 4.676149][ T0] Read of size 8 at addr 1fffffff85115558 by task swapper/0/0<br /> [ 4.683454][ T0]<br /> [ 4.685638][ T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.19.0-rc3-00004-g0e862838f290 #1<br /> [ 4.694331][ T0] Hardware name: Supermicro SYS-5018D-FN4T/X10SDV-8C-TLN4F, BIOS 1.1 03/02/2016<br /> [ 4.703196][ T0] Call Trace:<br /> [ 4.706334][ T0] <br /> [ 4.709133][ T0] ? dmar_parse_one_rhsa (arch/x86/include/asm/bitops.h:214 arch/x86/include/asm/bitops.h:226 include/asm-generic/bitops/instrumented-non-atomic.h:142 include/linux/nodemask.h:415 drivers/iommu/intel/dmar.c:497)<br /> <br /> after converting the type of the first argument (@nr, bit number)<br /> of arch_test_bit() from `long` to `unsigned long`[0].<br /> <br /> Under certain conditions (for example, when ACPI NUMA is disabled<br /> via command line), pxm_to_node() can return %NUMA_NO_NODE (-1).<br /> It is valid &amp;#39;magic&amp;#39; number of NUMA node, but not valid bit number<br /> to use in bitops.<br /> node_online() eventually descends to test_bit() without checking<br /> for the input, assuming it&amp;#39;s on caller side (which might be good<br /> for perf-critical tasks). There, -1 becomes %ULONG_MAX which leads<br /> to an insane array index when calculating bit position in memory.<br /> <br /> For now, add an explicit check for @node being not %NUMA_NO_NODE<br /> before calling test_bit(). The actual logics didn&amp;#39;t change here<br /> at all.<br /> <br /> [0] https://github.com/norov/linux/commit/0e862838f290147ea9c16db852d8d494b552d38d