Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53320nilfs2: 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]

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53320, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < e0a0c4903cbba351f0f5b5d104960d3a5b23202f
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 9472d37799a0b9ff9b99639f35961ac2f0b3c9be
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 65e07964b4b2daf9a54e686cf0fa72d74a9648a8
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < b88f905d4449b70da6bda547be546e365e44352e
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 4525658002be3ad310b16bf8db48c8adb6a55d32
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < e5ff0ba4b6983cdbcc826efc201e7179ece5d46f
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 94094e70fe292c9566502772d4d4d6d6a99204b1
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < be3e5d10643d3be1cbac9d9939f220a99253f980
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53320 badge
[![CVE-2026-53320](https://cveledger.app/badge/CVE-2026-53320.svg)](https://cveledger.app/cve/CVE-2026-53320)

Record last updated .