CVE-2026-46124 isofs: validate block number from NFS file handle in isofs_export_iget

High 7.5 Published Updated

An authenticated NFS peer can read adjacent partition data via crafted file handles in the Linux kernel isofs module, leading to information disclosure.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-46124?

CVE-2026-46124 is a high-severity vulnerability in Linux kernel, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-125

Which versions are affected by CVE-2026-46124?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-46124?

Apply the vendor's patch.

Is CVE-2026-46124 being exploited?

There is no known exploitation of CVE-2026-46124 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-88947, BELL-CVE-2026-46124, DEBIAN-CVE-2026-46124, GHSA-5599-pvjx-q3hc, ROOT-OS-DEBIAN-11-CVE-2026-46124, ROOT-OS-DEBIAN-12-CVE-2026-46124 and 3 more.

Is CVE-2026-46124 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free