CVE-2022-50864

nilfs2: fix shift-out-of-bounds due to too large exponent of block size

N/A
Published: December 30, 2025 at 12:15 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix shift-out-of-bounds due to too large exponent of block size If field s_log_block_size of superblock data is corrupted and too large, init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds warning followed by a kernel panic (if panic_on_warn is set): shift exponent 38973 is too large for 32-bit type 'int' Call Trace: <TASK> dump_stack_lvl+0xcd/0x134 ubsan_epilogue+0xb/0x50 __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5 init_nilfs.cold.11+0x18/0x1d [nilfs2] nilfs_mount+0x9b5/0x12b0 [nilfs2] ... This fixes the issue by adding and using a new helper function for getting block size with sanity check.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.30 ≤ v < 5.10.1632.6.30 ≤ v < 5.15.862.6.30 ≤ v < 6.0.162.6.30 ≤ v < 6.1.22.6.30 ≤ v < 6.22.6.308a9d2191e9f43bbcd256a9a6871bd73434c83f2f
Vendor states this is fixed in 8b6ef451b5701b37d9a5905534595776a662edfc (fixed)
Vendor states this is fixed in a16731fa1b96226c75bbf18e73513b14fc318360 (fixed)
Vendor states this is fixed in ddb6615a168f97b91175e00eda4c644741cf531c (fixed)
Vendor states this is fixed in ebeccaaef67a4895d2496ab8d9c2fb8d89201211 (fixed)
Vendor states this is fixed in ec93b5430ec0f60877a5388bb023d60624f9ab9f (fixed)
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card