CVE-2026-99311
udf: fix return value for non-recorded-allocated extents in udf_map_block()
What happened?
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 software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: c226964ec786f3797ed389a16392ce4357697d24 to < 0d7f6c2b3c07fa239ebc169280eba9932cc56f46; affected: c226964ec786f3797ed389a16392ce4357697d24 to < df713b82b4b9671c16b52b60f3412c677719e2b8; affected: c226964ec786f3797ed389a16392ce4357697d24 to < f022984a4a1c18aa9c506790eb47da000dce95a7; affected: c226964ec786f3797ed389a16392ce4357697d24 to < 0f242ca0878896df30292f4922700a32e8fdd039; affected: 493447dd8336607fce426f7879e581095f6c606e; affected: b22d9a5698abf04341f8fbc30141e0673863c3a6; affected: 6.6.59 to < 6.7; affected: 6.11.6 to < 6.12 | See vendor advisory |
| LinuxLinux | affected: 6.12; unaffected: 0 to < 6.12; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99311
- https://git.kernel.org/stable/c/0d7f6c2b3c07fa239ebc169280eba9932cc56f46
- https://git.kernel.org/stable/c/df713b82b4b9671c16b52b60f3412c677719e2b8
- https://git.kernel.org/stable/c/f022984a4a1c18aa9c506790eb47da000dce95a7
- https://git.kernel.org/stable/c/0f242ca0878896df30292f4922700a32e8fdd039