Linux Kernel up to 7.0.9 nilfs2 nilfs_ioctl_mark_blocks_dirty iteration

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability labeled as critical has been found in Linux Kernel up to 7.0.9. The impacted element is the function nilfs_ioctl_mark_blocks_dirty of the component nilfs2. The manipulation results in iteration. This vulnerability is known as CVE-2026-53320. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.0.9. It has been classified as critical. Affected is the function nilfs_ioctl_mark_blocks_dirty of the component nilfs2. The manipulation with an unknown input leads to a iteration vulnerability. CWE is classifying the issue as CWE-834. The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed. This is going to have an impact on availability. CVE summarizes:

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]

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-53320 since 06/09/2026. Technical details are known, but there is no available exploit.

Upgrading to version 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33 or 7.0.10 eliminates this vulnerability. Applying the patch e0a0c4903cbba351f0f5b5d104960d3a5b23202f/9472d37799a0b9ff9b99639f35961ac2f0b3c9be/65e07964b4b2daf9a54e686cf0fa72d74a9648a8/b88f905d4449b70da6bda547be546e365e44352e/4525658002be3ad310b16bf8db48c8adb6a55d32/e5ff0ba4b6983cdbcc826efc201e7179ece5d46f/94094e70fe292c9566502772d4d4d6d6a99204b1/be3e5d10643d3be1cbac9d9939f220a99253f980 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Iteration
CWE: CWE-834 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.258/5.15.209/6.1.175/6.6.141/6.12.91/6.18.33/7.0.10
Patch: e0a0c4903cbba351f0f5b5d104960d3a5b23202f/9472d37799a0b9ff9b99639f35961ac2f0b3c9be/65e07964b4b2daf9a54e686cf0fa72d74a9648a8/b88f905d4449b70da6bda547be546e365e44352e/4525658002be3ad310b16bf8db48c8adb6a55d32/e5ff0ba4b6983cdbcc826efc201e7179ece5d46f/94094e70fe292c9566502772d4d4d6d6a99204b1/be3e5d10643d3be1cbac9d9939f220a99253f980

Timelineinfo

06/09/2026 CVE reserved
06/26/2026 +17 days Advisory disclosed
06/26/2026 +0 days VulDB entry created
06/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53320 (🔒)
GCVE (CVE): GCVE-0-2026-53320
GCVE (VulDB): GCVE-100-374370

Entryinfo

Created: 06/26/2026 22:29
Changes: 06/26/2026 22:29 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!