Description
In the Linux kernel, the following vulnerability has been resolved: udf: fix return value for non-recorded-allocated extents in udf_map_block() When someone creates a corrupted UDF filesystem where symlink contains other extent type than EXT_RECORDED_ALLOCATED, it can leads to a crash like: Oops: general protection fault KASAN: maybe wild-memory-access RIP: 0010:page_get_link (fs/namei.c:6503) Call Trace: vfs_readlink (fs/namei.c:6419) do_readlinkat (fs/stat.c:583) __x64_sys_readlink (fs/stat.c:605 fs/stat.c:602 fs/stat.c:602) This is because in this case udf_map_block() fails to convert return value of inode_bmap() from 1 to 0. Returned '1' propagates through udf_bread() all the way up to __page_get_link() where it ends up being treated as a folio pointer with obvious results. Move the reset to 0 line outside the if, so udf_map_block() returns either 0 or -errno, even if the extent type is not EXT_RECORDED_ALLOCATED.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
c226964ec786f3797ed389a16392ce4357697d24 to < 0d7f6c2b3c07fa239ebc169280eba9932cc56f46affectedc226964ec786f3797ed389a16392ce4357697d24 to < df713b82b4b9671c16b52b60f3412c677719e2b8affectedc226964ec786f3797ed389a16392ce4357697d24 to < f022984a4a1c18aa9c506790eb47da000dce95a7affectedc226964ec786f3797ed389a16392ce4357697d24 to < 0f242ca0878896df30292f4922700a32e8fdd039affected493447dd8336607fce426f7879e581095f6c606eaffectedb22d9a5698abf04341f8fbc30141e0673863c3a6affected6.6.59 to < 6.7affected6.11.6 to < 6.12affected
Linux Linux
Default version status: affected
6.12affected0 to < 6.12unaffected6.12.117 to ≤ 6.12.*unaffected6.18.61 to ≤ 6.18.*unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected