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.
Published: 2026-06-08
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises in the Linux kernel's ISO 9660 file system support, where the Rock Ridge continuation extent value is read from an ISO image without validating that the block number is within the bounds of the mounted volume. The unchecked block number can cause the kernel to read data from any location on the underlying block device, including areas belonging to a different filesystem. The data read is interpreted as Rock Ridge records, and only the text of SL sub‑records is then made reachable through readlink(2). This allows a narrow information‑leak channel that could reveal filenames or other string data outside the protected ISO image.

Affected Systems

All systems running a Linux kernel that includes the isofs module before the fixes in commits e595447e177b and f54e18f1b831 are potentially vulnerable. The exact kernel version range was not specified in the advisory, so any kernel with the isofs driver and no subsequent patch is at risk until an updated kernel or module is installed.

Risk and Exploitability

There is no memory‑safety issue or privilege escalation path; the only effect is a potential leakage of strings from a neighboring filesystem if the malicious ISO is mounted. The acceptable block read that fails cleanly returns NULL via the block layer, so no kernel crash occurs. The CVSS score is not provided and the EPSS score is not available. The vulnerability is not listed in CISA's KEV catalog. An attacker would need the ability to mount a crafted ISO image, either through the automatic udisks2 mount or by executing a mount command with CAP_SYS_ADMIN. Because the data exposed is limited and requires privileged access or user interaction, the practical risk is relatively low.

Generated by OpenCVE AI on June 8, 2026 at 19:08 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the kernel to a version that incorporates the bounds‑check fix introduced in commits e595447e177b and f54e18f1b831.
  • Disable or restrict automatic mounting of optical media via udisks2 so that only trusted users can trigger ISO mounts.
  • Ensure that only privileged users with the CAP_SYS_ADMIN capability can perform mount operations, or enforce least‑privilege policies to limit mounting of ISO filesystems.

Generated by OpenCVE AI on June 8, 2026 at 19:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 08 Jun 2026 19:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-200

Mon, 08 Jun 2026 17:00:00 +0000

Type Values Removed Values Added
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.
Title isofs: validate Rock Ridge CE continuation extent against volume size
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-06-08T15:46:30.642Z

Reserved: 2026-05-13T15:03:33.111Z

Link: CVE-2026-46303

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-06-08T17:16:48.853

Modified: 2026-06-08T17:16:48.853

Link: CVE-2026-46303

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-08T22:15:33Z

Weaknesses