LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50864 is a Linux kernel NILFS2 filesystem bug. A corrupted NILFS2 superblock can cause an internal shift error during mount or load. If the system is configured to panic on warnings, this can crash the kernel. Business risk is mainly availability, especially where systems handle untrusted disk images or removable media.

Executive priority

Prioritize patching where Linux systems mount untrusted storage or images, or where kernel panic would disrupt critical services. For typical servers not using NILFS2, treat as routine kernel maintenance unless vendor guidance indicates otherwise.

Technical view

The issue is in Linux kernel nilfs2. An oversized corrupted s_log_block_size value can reach init_nilfs() or load_nilfs(), causing a shift-out-of-bounds UBSAN warning and potential kernel panic when panic_on_warn is enabled. The upstream resolution adds a helper to calculate block size with sanity checking.

Likely exposure

Exposure is most relevant on Linux systems with NILFS2 support that mount NILFS2 filesystems from untrusted or corrupt media/images. Systems not using NILFS2, or not mounting untrusted filesystems, likely have lower exposure. The CVE data does not provide a CVSS score.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. Practical abuse appears to require getting a vulnerable system to process a malformed NILFS2 filesystem. The documented impact is kernel warning and possible panic, not code execution.

Researcher notes

Evidence is limited to the CVE record and upstream stable commits. The sources describe a bounds/sanity-check flaw in NILFS2 block size handling. No CVSS, CWE, public exploit, or distribution-specific advisory is included in the provided bundle.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable NILFS2 fixes.
  • Check your Linux distribution’s advisory for backported fixes and supported kernel versions.
  • Avoid mounting untrusted NILFS2 filesystems or disk images until fixed.
  • If NILFS2 is unnecessary, consult platform guidance on disabling unused filesystem support.

Validation and detection

  • Inventory Linux kernels and determine whether NILFS2 support is enabled or loadable.
  • Confirm the running kernel includes the referenced upstream stable fix or vendor backport.
  • Review workflows that mount removable media, forensic images, or user-supplied filesystems.
  • Check whether panic_on_warn is enabled on systems in scope.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50864 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8a9d2191e9f43bbcd256a9a6871bd73434c83f2f, 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f, 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f, 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f, 8a9d2191e9f43bbcd256a9a6871bd73434c83f2funaffected
LinuxLinux2.6.30, 0, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.