dbcve.org
Linux KernelOperating system · Linux

CVE-2026-46124

HIGH · 7.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 5.5 / 5.10.258 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: isofs: validate block number from NFS file handle in isofs_export_iget isofs_fh_to_dentry() and isofs_fh_to_parent() pass an attacker- controlled block number (ifid->block or ifid->parent_block) from the NFS file handle to isofs_export_iget(), which only rejects block == 0 before calling isofs_iget() and ultimately sb_bread(). A crafted file handle with fh_len sufficient to pass the check added by commit 0405d4b63d08 ("isofs: Prevent the use of too small fid") can still drive the server to read any in-range block on the backing device as if it were an iso_directory_record. That earlier fix was assigned CVE-2025-37780. sb_bread() on an out-of-range block returns NULL cleanly via the EIO path, so there is no memory-safety violation. For in-range reads of adjacent-partition data on the same block device, the unrelated bytes end up in iso_inode_info fields that reach the NFS client as dentry metadata. The deployment surface (isofs exported over NFS from loop-mounted images) is narrow and requires an authenticated NFS peer, but the malformed-file-handle class is reportable as hardening next to the existing CVE-2025-37780 fix. Reject block >= ISOFS_SB(sb)->s_nzones in isofs_export_iget() so the check covers both isofs_fh_to_dentry() and isofs_fh_to_parent() call sites with a single line.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.4.293, < 5.5>= 5.10.237, < 5.10.258>= 5.15.181, < 5.15.209>= 6.1.135, < 6.1.175>= 6.6.88, < 6.6.140>= 6.12.25, < 6.12.88>= 6.14.4, < 6.15>= 6.15.1, < 6.18.30>= 6.19, < 7.0.7= 6.15= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.5 / 5.10.258 / 5.15.209 or later
Fixed in 5.55.10.2585.15.209
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel 5.10.258, 5.15.209, 6.1.175, or later stable releases

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Check if the kernel version falls within the affected range: >= 5.4.293 and < 5.5, >= 5.10.237 and < 5.10.258, >= 5.15.181 and < 5.15.209, or >= 6.1.135 and < 6.1.175
  3. 3. For affected kernels, upgrade to the next stable release that includes the fix:
  4. - For 5.4.x kernels: upgrade to 5.5 or later stable release
  5. - For 5.10.x kernels: upgrade to 5.10.258 or later
  6. - For 5.15.x kernels: upgrade to 5.15.209 or later
  7. - For 6.1.x kernels: upgrade to 6.1.175 or later
  8. 4. Apply the upgrade via your distribution's package manager (e.g., `apt-get update && apt-get upgrade`, `yum update`, or `dnf update`)
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with older drivers or modules; ensure critical modules are compatible with the new kernel version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46124 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data