Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97485 Overview
CVE-2026-97485 is a Linux kernel vulnerability in the OMFS (Optimized MPEG Filesystem) implementation. The flaw stems from unhandled set_blocksize failures when mounting an OMFS filesystem whose block size exceeds PAGE_SIZE. OMFS uses buffer_heads, which do not handle block sizes larger than the system page size correctly. Without the fix, the first __bread_gfp call during mount triggers a BUG_ON(offset >= folio_size(folio)) assertion inside folio_set_bh, resulting in a kernel bug and denial of service. The issue has been resolved upstream in the stable kernel tree.
Critical Impact
A local user with the ability to mount an OMFS filesystem image can crash the kernel through a BUG_ON assertion failure during the mount path.
Affected Products
- Linux kernel OMFS filesystem driver (fs/omfs)
- Stable kernel branches prior to the commits referenced below
- Systems with OMFS compiled in or available as a loadable module
Discovery Timeline
- 2026-09-24 - CVE-2026-97485 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-97485
Vulnerability Analysis
The OMFS driver calls set_blocksize() during mount to configure the block device for the filesystem's declared block size. On systems where the OMFS block size exceeds PAGE_SIZE, set_blocksize() returns an error that the driver previously ignored. The mount path then proceeds to call __bread_gfp() to read filesystem metadata using buffer_heads. Buffer_heads cannot represent blocks larger than a folio, so the subsequent call into folio_set_bh() violates the invariant offset < folio_size(folio) and trips the BUG_ON assertion. The result is a kernel panic or oops on the mounting CPU, taking down the affected process context and potentially the system depending on configuration.
Root Cause
The root cause is missing error handling for set_blocksize() return values in the OMFS mount routine. The code assumed success and continued to buffer_head-based I/O without validating that the requested block size was supported for the underlying device and page size.
Attack Vector
Exploitation requires the ability to mount a crafted OMFS image. In most hardened configurations this requires CAP_SYS_ADMIN, but environments that auto-mount removable media or allow unprivileged user namespace mounts broaden the exposure. A specially crafted image declaring a block size greater than PAGE_SIZE is sufficient to trigger the assertion. No code execution primitive is demonstrated; the observed impact is a kernel-level denial of service via BUG_ON.
Verified kernel patches are available in the stable tree. Refer to the upstream commits for the exact diff: Kernel Git Commit 18c3d6f, Kernel Git Commit 61ffc31c, and Kernel Git Commit fd4d6593.
Detection Methods for CVE-2026-97485
Indicators of Compromise
- Kernel log entries referencing BUG_ON in folio_set_bh triggered during an OMFS mount operation.
- dmesg call traces containing __bread_gfp, omfs_fill_super, or set_blocksize immediately preceding a kernel oops.
- Unexpected system crashes or hangs correlated with mount -t omfs activity or removable media insertion.
Detection Strategies
- Inventory running kernels and compare build versions against the fixed stable releases referenced in the upstream commits.
- Audit systems where the omfs module is loaded (lsmod | grep omfs) and determine whether loading can be restricted via module blacklisting.
- Monitor for mount syscalls specifying omfs as the filesystem type, particularly from non-root contexts or user namespaces.
Monitoring Recommendations
- Forward kernel ring-buffer (/dev/kmsg) and journald events to a centralized log pipeline and alert on BUG: or Oops: records containing folio_set_bh or omfs.
- Track mount events using auditd rules on the mount syscall to establish a baseline and flag anomalous filesystem types.
- Correlate host crash telemetry with recent removable-media or image-mount events to identify likely trigger sources.
How to Mitigate CVE-2026-97485
Immediate Actions Required
- Apply the upstream stable kernel update that includes the referenced commits and reboot affected hosts.
- Blacklist the omfs kernel module on systems that do not require OMFS support by adding blacklist omfs to /etc/modprobe.d/.
- Restrict unprivileged mount operations by disabling user namespaces where not required (sysctl kernel.unprivileged_userns_clone=0 on supported distributions).
Patch Information
The fix adds proper handling of set_blocksize() failures in the OMFS mount path, aborting the mount cleanly when the requested block size cannot be honored. The upstream commits are available in the stable tree: Kernel Git Commit 18c3d6f, Kernel Git Commit 61ffc31c, and Kernel Git Commit fd4d6593. Distribution vendors will ship these in their next stable kernel updates.
Workarounds
- Prevent loading of the omfs module on systems that do not need it, eliminating the attack surface entirely.
- Disable auto-mount of removable media in desktop environments (for example, via udisks or GNOME media-automount settings) to prevent untrusted images from being mounted.
- Limit CAP_SYS_ADMIN and container mount capabilities to trusted workloads only.
# Blacklist the omfs module until a patched kernel is deployed
echo 'blacklist omfs' | sudo tee /etc/modprobe.d/blacklist-omfs.conf
echo 'install omfs /bin/true' | sudo tee -a /etc/modprobe.d/blacklist-omfs.conf
sudo depmod -a
sudo update-initramfs -u
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

