Linux Kernel up to 7.1-rc1 isofs rock.c rock_continue cont_extent infinite loop

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability categorized as critical has been discovered in Linux Kernel up to 7.1-rc1. The impacted element is the function rock_continue of the file rock.c of the component isofs. Executing a manipulation of the argument cont_extent can lead to infinite loop. The identification of this vulnerability is CVE-2026-46303. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 7.1-rc1. This vulnerability affects the function rock_continue of the file rock.c of the component isofs. The manipulation of the argument cont_extent with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-46303 since 05/13/2026. There are known technical details, but no exploit is available.

Upgrading to version 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc2 eliminates this vulnerability. Applying the patch 8356fb821016797f5677cbeee5ddc0d32a95b4be/d582e12378bc1637f337622feef762f53c43fd57/bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9/c9b37c8b73f6368e4750e5ccb0632c380b43c6e5/22b36fa081f38ab397c7697f9d539211b51a0cfc/e69da8eeab74b4f4505024c38a17bce060fe7df8/ef048470c90bc8c1b8318bb2ce329da9ef64b9fe/a36d990f591320e9dd379ab30063ebfe91d47e1f is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.258/5.15.209/6.1.175/6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc2
Patch: 8356fb821016797f5677cbeee5ddc0d32a95b4be/d582e12378bc1637f337622feef762f53c43fd57/bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9/c9b37c8b73f6368e4750e5ccb0632c380b43c6e5/22b36fa081f38ab397c7697f9d539211b51a0cfc/e69da8eeab74b4f4505024c38a17bce060fe7df8/ef048470c90bc8c1b8318bb2ce329da9ef64b9fe/a36d990f591320e9dd379ab30063ebfe91d47e1f

Timelineinfo

05/13/2026 CVE reserved
06/08/2026 +26 days Advisory disclosed
06/08/2026 +0 days VulDB entry created
06/08/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46303 (🔒)
GCVE (CVE): GCVE-0-2026-46303
GCVE (VulDB): GCVE-100-369244

Entryinfo

Created: 06/08/2026 20:12
Changes: 06/08/2026 20:12 (61)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!