cbcvebase.
CVE-2026-46303
published 2026-06-08

CVE-2026-46303: In the Linux kernel, the following vulnerability has been resolved: isofs: validate Rock Ridge CE continuation extent against volume size rock_continue() reads…

PriorityP344high8.2CVSS 3.1
AVNACLPRNUINSUCHILAN
EPSS
0.28%
20.0th percentile
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.

Affected

50 ranges· showing 25
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux
linuxlinux>= 2.6.32.66 < 2.6.332.6.33
linuxlinux>= 3.10.64 < 3.113.11
linuxlinux>= 3.12.36 < 3.133.13
linuxlinux>= 3.14.28 < 3.153.15
linuxlinux>= 3.17.8 < 3.183.18
linuxlinux>= 3.18.2 < 3.193.19
linuxlinux>= 3.2.67 < 3.33.3
linuxlinux>= 3.4.107 < 3.53.5
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < 8356fb821016797f5677cbeee5ddc0d32a95b4be8356fb821016797f5677cbeee5ddc0d32a95b4be
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < d582e12378bc1637f337622feef762f53c43fd57d582e12378bc1637f337622feef762f53c43fd57
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < c9b37c8b73f6368e4750e5ccb0632c380b43c6e5c9b37c8b73f6368e4750e5ccb0632c380b43c6e5
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < 22b36fa081f38ab397c7697f9d539211b51a0cfc22b36fa081f38ab397c7697f9d539211b51a0cfc
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < e69da8eeab74b4f4505024c38a17bce060fe7df8e69da8eeab74b4f4505024c38a17bce060fe7df8
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < ef048470c90bc8c1b8318bb2ce329da9ef64b9feef048470c90bc8c1b8318bb2ce329da9ef64b9fe
linuxlinux>= f54e18f1b831c92f6512d2eedb224cd63d607d3d < a36d990f591320e9dd379ab30063ebfe91d47e1fa36d990f591320e9dd379ab30063ebfe91d47e1f

CVSS provenance

nvdv3.18.2HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
vendor_redhat8.2HIGH
vendor_ubuntu7.0HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.