Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99311udf: fix return value for non-recorded-allocated extents in udf_map_block()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 52 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected c226964ec786f3797ed389a16392ce4357697d24 – < 0d7f6c2b3c07fa239ebc169280eba9932cc56f46
    • affected c226964ec786f3797ed389a16392ce4357697d24 – < df713b82b4b9671c16b52b60f3412c677719e2b8
    • affected c226964ec786f3797ed389a16392ce4357697d24 – < f022984a4a1c18aa9c506790eb47da000dce95a7
    • affected c226964ec786f3797ed389a16392ce4357697d24 – < 0f242ca0878896df30292f4922700a32e8fdd039
    • affected 493447dd8336607fce426f7879e581095f6c606e
    • affected b22d9a5698abf04341f8fbc30141e0673863c3a6
    • affected 6.6.59 – < 6.7
    • affected 6.11.6 – < 6.12
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 6.12.117 – ≤ 6.12.*
    • unaffected 6.18.61 – ≤ 6.18.*
    • unaffected 7.3.2 – ≤ 7.3.*
    • unaffected 7.4-rc1 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99311 badge
[![CVE-2026-99311](https://cveledger.app/badge/CVE-2026-99311.svg)](https://cveledger.app/cve/CVE-2026-99311)

Record last updated .