CVE-2026-99311

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.

Severity
not scored
CVSS v3
not scored
The CNA gave no score; NVD has not scored it yet.
Exploit chance (EPSS)
0.157%
chance of exploitation in the next 30 days
higher than 4.9% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Timeline

  1. 2026-11-16Published by the CNA09:59 UTC
  2. 2026-11-16Published in NVD10:17 UTC · 17 minutes after the CNA

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
linux linuxfrom 6.11.6 before 6.12fixed in 6.12from 6.6.59 before 6.7fixed in 6.76.126.7
linux linux_kernelfrom 6.12 before 6.12.117fixed in 6.12.117from 6.12 before 6.18.61fixed in 6.18.61from 6.12 before 7.3.2fixed in 7.3.2from 6.12 before 7.4-rc1fixed in 7.4-rc1from 6.11.6no fix listed(+1 more)6.12.1176.18.617.3.27.4-rc1not listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources