5.5
MEDIUM CVSS 3.1
CVE-2026-53320
nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty()
Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() nilfs_ioctl_mark_blocks_dirty() uses bd_oblocknr to detect dead blocks by comparing it with the current block number bd_blocknr. If they differ, the block is considered dead and skipped. However, bd_oblocknr should never be 0 since block 0 typically stores the primary superblock and is never a valid GC target block. A corrupted ioctl request with bd_oblocknr set to 0 causes the comparison to incorrectly match when the lookup returns -ENOENT and sets bd_blocknr to 0, bypassing the dead block check and calling nilfs_bmap_mark() on a non-existent block. This causes nilfs_btree_do_lookup() to return -ENOENT, triggering the WARN_ON(ret == -ENOENT). Fix this by rejecting ioctl requests with bd_oblocknr set to 0 at the beginning of each iteration. [ryusuke: slightly modified the commit message and comments for accuracy]

INFO

Published Date :

June 26, 2026, 8:17 p.m.

Last Modified :

July 6, 2026, 8:12 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-53320 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update the Linux kernel to reject invalid block numbers in the nilfs2 module.
  • Update the Linux kernel.
  • Apply the fix for nilfs2 module.
  • Ensure bd_oblocknr is not zero.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-53320 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-53320 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-53320 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-53320 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Jul. 06, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE NVD-CWE-noinfo
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.141 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.91 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.175 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.209 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.30 up to (excluding) 5.10.258
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/4525658002be3ad310b16bf8db48c8adb6a55d32 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/65e07964b4b2daf9a54e686cf0fa72d74a9648a8 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/94094e70fe292c9566502772d4d4d6d6a99204b1 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/9472d37799a0b9ff9b99639f35961ac2f0b3c9be Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/b88f905d4449b70da6bda547be546e365e44352e Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/be3e5d10643d3be1cbac9d9939f220a99253f980 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/e0a0c4903cbba351f0f5b5d104960d3a5b23202f Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/e5ff0ba4b6983cdbcc826efc201e7179ece5d46f Types: Patch
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jun. 26, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': 'e0a0c4903cbba351f0f5b5d104960d3a5b23202f', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': '9472d37799a0b9ff9b99639f35961ac2f0b3c9be', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': '65e07964b4b2daf9a54e686cf0fa72d74a9648a8', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': 'b88f905d4449b70da6bda547be546e365e44352e', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': '4525658002be3ad310b16bf8db48c8adb6a55d32', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': 'e5ff0ba4b6983cdbcc826efc201e7179ece5d46f', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': '94094e70fe292c9566502772d4d4d6d6a99204b1', 'versionType': 'git'}, {'status': 'affected', 'version': '7942b919f7321f95a777d396ff7894a7a83dc9b0', 'lessThan': 'be3e5d10643d3be1cbac9d9939f220a99253f980', 'versionType': 'git'}], 'programFiles': ['fs/nilfs2/ioctl.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2.6.30'}, {'status': 'unaffected', 'version': '0', 'lessThan': '2.6.30', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.258', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.209', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.175', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.141', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.91', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.33', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.10', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/nilfs2/ioctl.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() nilfs_ioctl_mark_blocks_dirty() uses bd_oblocknr to detect dead blocks by comparing it with the current block number bd_blocknr. If they differ, the block is considered dead and skipped. However, bd_oblocknr should never be 0 since block 0 typically stores the primary superblock and is never a valid GC target block. A corrupted ioctl request with bd_oblocknr set to 0 causes the comparison to incorrectly match when the lookup returns -ENOENT and sets bd_blocknr to 0, bypassing the dead block check and calling nilfs_bmap_mark() on a non-existent block. This causes nilfs_btree_do_lookup() to return -ENOENT, triggering the WARN_ON(ret == -ENOENT). Fix this by rejecting ioctl requests with bd_oblocknr set to 0 at the beginning of each iteration. [ryusuke: slightly modified the commit message and comments for accuracy]
    Added Reference https://git.kernel.org/stable/c/4525658002be3ad310b16bf8db48c8adb6a55d32
    Added Reference https://git.kernel.org/stable/c/65e07964b4b2daf9a54e686cf0fa72d74a9648a8
    Added Reference https://git.kernel.org/stable/c/94094e70fe292c9566502772d4d4d6d6a99204b1
    Added Reference https://git.kernel.org/stable/c/9472d37799a0b9ff9b99639f35961ac2f0b3c9be
    Added Reference https://git.kernel.org/stable/c/b88f905d4449b70da6bda547be546e365e44352e
    Added Reference https://git.kernel.org/stable/c/be3e5d10643d3be1cbac9d9939f220a99253f980
    Added Reference https://git.kernel.org/stable/c/e0a0c4903cbba351f0f5b5d104960d3a5b23202f
    Added Reference https://git.kernel.org/stable/c/e5ff0ba4b6983cdbcc826efc201e7179ece5d46f
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.