MySQL 5.7.32 includes the following InnoDB changes:

Not applicable to MariaDB Server

Bug#30950714 CONSISTENT SNAPSHOT CAN BE CORRUPTED BY OTHER TRANSACTIONS
Bug#31205266 : CONCURRENT UPDATE CAUSE CRASH IN ROW_SEARCH_MVCC (revert, re-apply, fixup)
These are follow-up fixes to Bug#23481444 OPTIMISER CALL ROW_SEARCH_MVCC() AND READ THE INDEX APPLIED BY UNCOMMITTED ROWS, which we chose not to apply to MariaDB already in MDEV-11751.

Bug #31560679 INNODB INTERNAL TEMP TABLE PRODUCES INCORRECT RESULTS
SQL execution in MariaDB never used InnoDB for temporary tables, and MDEV-11487 removed that code.

Bug#31313533 : IMPORT FAILS FOR ENCRYP AND COMPRESSION ENABLED TDE TABLES (fixup)
Bug#31817270 : MTR TEST FAILURE IN I_INNODB.TABLE_COMPRESS_4 FOR 8K PAGE SIZE
These are related to the MySQL 5.7 reimplementation of the MariaDB 10.1 features for encrypted or sparse-file page_compressed storage of InnoDB data files.

Bug #30594501 QUERY STALLS IN "QUERY END" STATUS FOR LONG TIME
This is also known as MySQL Bug#91078. A comment on that page says:

This is a real bug, and there is one fix in 8.0.22 and 5.7.32 that may solve it. Please wait for that release, and search the change history notes for Bug #30594501 . It is related to previously fixed Bug #27325898 .

In MDEV-17536 (Merge new release of InnoDB 5.7.24 to 10.2) we concluded that the earlier change is not applicable to MariaDB, so neither should this follow-up fix be:

Bug #27325898 - INNODB: ASSERTION FAILURE IN THREAD 139686919030528 IN FILE TRX0TRX.IC LINE 213 is not applicable, because we already removed the TrxInInnoDB code and trx->lock.start_stmt in MDEV-13935.

Applicable to MariaDB Server

Bug #30607708 IF ANALYZE TABLE RUNS MORE THAN 600 SECONDS DIAGNOSTIC QUERY MAY CRASH SERVER
To be addressed in MDEV-23991.

Bug #31105262 LATCHCOUNTER::ITERATE SHOULD USE M_MUTEX PROTECTION
To be addressed in MDEV-23996.

Bug #31036301 ASSERTION FAILURE: SYNC0RW.IC:429:LOCK->LOCK_WORD
This one we had previously filed as MDEV-23693, and the fix is applicable for that bug.

Bug #30933728 INNODB FTS PHRASE SEARCH HIT AN ASSERT
Bug #31228694 FTS QUERY WITH LIMIT HIT AN ASSERT
The test cases for these depend on the n-gram search that we will not have before MDEV-10267, but the code changes looked innocent enough to be applied. These are now in 10.2.

Bug #29929684 USING MANY NESTED ARGUMENTS WITH BOOLEAN FTS CAN LEAD TO TERMINATE SERVER.
Addressed by MDEV-23999.