udf: fix return value for non-recorded-allocated extents in udf_map_block()
Published Nov 16, 2026 · Updated Nov 16, 2026
In the Linux kernel, the following vulnerability has been resolved:
Summary
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.
The record
- CVE
- CVE-2026-99311
- Published
- Nov 16, 2026
- Updated
- Nov 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 16, 2026CVE publishedPublication date reported by the CVE source.
- Nov 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=493447dd8336607fce426f7879e581095f6c606e
- Affected versionversion=6.11.6 <6.12
- Affected versionversion=6.12
- Affected versionversion=6.6.59 <6.7
- Affected versionversion=b22d9a5698abf04341f8fbc30141e0673863c3a6
- Affected versionversion=c226964ec786f3797ed389a16392ce4357697d24 <0d7f6c2b3c07fa239ebc169280eba9932cc56f46
- Affected versionversion=c226964ec786f3797ed389a16392ce4357697d24 <0f242ca0878896df30292f4922700a32e8fdd039
- Affected versionversion=c226964ec786f3797ed389a16392ce4357697d24 <df713b82b4b9671c16b52b60f3412c677719e2b8
- Affected versionversion=c226964ec786f3797ed389a16392ce4357697d24 <f022984a4a1c18aa9c506790eb47da000dce95a7
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us