Menu

Star on GitHub · 3.2k

CVE-2026-53320

5.5 · MEDIUM

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 d…

Published Jun 26, 2026EPSS 0.17%

Overview

CVE-2026-53320 is a medium-severity vulnerability. It was published on June 26, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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]

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-53320?

CVE-2026-53320 is a medium-severity vulnerability. It was published on June 26, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-53320?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-53320?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53320?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53320 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all