CVE-2026-46303: isofs: validate Rock Ridge CE continuation extent against volume size
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2.6.33, 22b36fa081f38ab397c7697f9d539211b51a0cfc, 3.11; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
Low priority for now. Upgrade to Linux Linux 2.6.33, 22b36fa081f38ab397c7697f9d539211b51a0cfc, 3.11; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Jun 8, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-401
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.32.66 and later · before 2.6.33
- linux linux kernel3.2.67 and later · before 3.3
- linux linux kernel3.4.107 and later · before 3.5
- linux linux kernel3.10.64 and later · before 3.11
- linux linux kernel3.12.36 and later · before 3.13
- linux linux kernel3.14.28 and later · before 3.15
- linux linux kernel3.17.8 and later · before 3.18
- linux linux kernel3.18.2 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.88
- linux linux kernel6.13 and later · before 6.18.30
- linux linux kernel6.19 and later · before 7.0.7
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 08313e26e06d4aa9ce1cbba1a8e359e9cab9ad56, 212c4d33ca83e2144064fe9c2911607fbed5386f, 96e44adce250199ec9b2b928be66365779ff1b59, 1fe5620fcd6c2f0a4a927ee10c8e53196da392f3, fbce0d7dc8965c9fb8d411862040239d4a768c71, 8190393a88f2b0321263a54f2a9eb5a2aa43be7e, 486aa789eadcf44ed87f972b209299c516454693, b6d20edb6e7cedb4eedb9e0193d20dd488ebae84, 3.19affected
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before 8356fb821016797f5677cbeee5ddc0d32a95b4beaffected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before d582e12378bc1637f337622feef762f53c43fd57affected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9affected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before c9b37c8b73f6368e4750e5ccb0632c380b43c6e5affected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before 22b36fa081f38ab397c7697f9d539211b51a0cfcaffected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before e69da8eeab74b4f4505024c38a17bce060fe7df8affected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before ef048470c90bc8c1b8318bb2ce329da9ef64b9feaffected · git
- f54e18f1b831c92f6512d2eedb224cd63d607d3d and later · before a36d990f591320e9dd379ab30063ebfe91d47e1faffected · git
- 2.6.32.66 and later · before 2.6.33affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.42.1.el10_2 | 6.12.0-211.42.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46298Jun 8, 2026 · pseries/papr-hvpipe: Fix race with interrupt handler18Monitor
- ← EarlierCVE-2026-46302Jun 8, 2026 · selinux: allow multiple opens of /sys/fs/selinux/policy22Monitor
- Later →CVE-2026-46304Jun 8, 2026 · nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2.6.33 | Vendor (CNA) |
| Linux Linux | 22b36fa081f38ab397c7697f9d539211b51a0cfc | Vendor (CNA) |
| Linux Linux | 3.11 | Vendor (CNA) |
| Linux Linux | 3.13 | Vendor (CNA) |
| Linux Linux | 3.15 | Vendor (CNA) |
| Linux Linux | 3.18 | Vendor (CNA) |
| Linux Linux | 3.19 | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 3.5 | Vendor (CNA) |
| Linux Linux | 8356fb821016797f5677cbeee5ddc0d32a95b4be | Vendor (CNA) |
| Linux Linux | a36d990f591320e9dd379ab30063ebfe91d47e1f | Vendor (CNA) |
| Linux Linux | bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9 | Vendor (CNA) |
| Linux Linux | c9b37c8b73f6368e4750e5ccb0632c380b43c6e5 | Vendor (CNA) |
| Linux Linux | d582e12378bc1637f337622feef762f53c43fd57 | Vendor (CNA) |
| Linux Linux | e69da8eeab74b4f4505024c38a17bce060fe7df8 | Vendor (CNA) |
| Linux Linux | ef048470c90bc8c1b8318bb2ce329da9ef64b9fe | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.42.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
+13
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/8356fb821016797f5677cbeee5ddc0d32a95b4be
- git.kernel.org/stable/c/a36d990f591320e9dd379ab30063ebfe91d47e1f
- git.kernel.org/stable/c/bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9
- git.kernel.org/stable/c/c9b37c8b73f6368e4750e5ccb0632c380b43c6e5
- git.kernel.org/stable/c/d582e12378bc1637f337622feef762f53c43fd57
- git.kernel.org/stable/c/e69da8eeab74b4f4505024c38a17bce060fe7df8
- git.kernel.org/stable/c/ef048470c90bc8c1b8318bb2ce329da9ef64b9fe
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.