{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.117-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.3.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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.",
  "id": "DEBIAN-CVE-2026-99311",
  "modified": "2026-11-17T04:47:59.616981130Z",
  "published": "2026-11-16T10:17:06.633Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99311"
    }
  ],
  "upstream": [
    "CVE-2026-99311"
  ]
}