CVE-2026-53320

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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]

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (8)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e5ff0ba4b6983cdbcc826efc201e7179ece5d46f
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e0a0c4903cbba351f0f5b5d104960d3a5b23202f
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be3e5d10643d3be1cbac9d9939f220a99253f980
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b88f905d4449b70da6bda547be546e365e44352e
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9472d37799a0b9ff9b99639f35961ac2f0b3c9be
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94094e70fe292c9566502772d4d4d6d6a99204b1
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65e07964b4b2daf9a54e686cf0fa72d74a9648a8
generic

nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4525658002be3ad310b16bf8db48c8adb6a55d32

Vendor Advisories for CVE-2026-53320(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-18ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-18ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-18ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-18ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-18ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-18ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-18ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-18ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-18ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 07:07 UTCEG score recompute
  3. 2026-09-18 07:07 UTCVendor advisory
  4. 2026-09-18 07:07 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 00:57 UTCEG score recompute
  8. 2026-09-14 00:57 UTCVendor advisory
  9. 2026-09-14 00:56 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 15:21 UTCEG score recompute
  12. 2026-09-12 15:21 UTCVendor advisory
  13. 2026-09-12 15:20 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 14:51 UTCEG score recompute
  19. 2026-09-06 14:51 UTCVendor advisory
  20. 2026-09-06 14:51 UTCGHSA enrichment
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 19:15 UTCEG score recompute
  2. 2026-08-30 19:15 UTCVendor advisory
  3. 2026-08-30 19:14 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 22:54 UTCEG score recompute
  7. 2026-08-27 22:54 UTCVendor advisory
  8. 2026-08-27 22:53 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 12:45 UTCEG score recompute
  13. 2026-08-24 12:45 UTCVendor advisory
  14. 2026-08-24 12:45 UTCGHSA enrichment
  15. 2026-08-23 10:36 UTCVendor advisory
  16. 2026-08-23 10:36 UTCGHSA enrichment
  17. 2026-08-22 09:20 UTCEG score recompute
  18. 2026-08-22 09:20 UTCVendor advisory
  19. 2026-08-22 09:20 UTCGHSA enrichment
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 07:47 UTCEG score recompute
  22. 2026-08-21 07:47 UTCVendor advisory
  23. 2026-08-21 07:47 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 06:32 UTCEG score recompute
  26. 2026-08-20 06:32 UTCVendor advisory
  27. 2026-08-20 06:31 UTCGHSA enrichment
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 23:30 UTCEG score recompute
  30. 2026-08-18 23:30 UTCVendor advisory
  31. 2026-08-18 23:30 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 06:40 UTCEG score recompute
  35. 2026-08-17 06:40 UTCVendor advisory
  36. 2026-08-17 06:40 UTCGHSA enrichment
  37. 2026-08-16 14:56 UTCEPSS rescore
  38. 2026-08-16 05:25 UTCEG score recompute
  39. 2026-08-16 05:25 UTCVendor advisory
  40. 2026-08-16 05:25 UTCGHSA enrichment
  41. 2026-08-16 02:14 UTCEPSS rescore
  42. 2026-08-15 04:10 UTCEG score recompute
  43. 2026-08-15 04:10 UTCVendor advisory
  44. 2026-08-15 04:10 UTCGHSA enrichment
  45. 2026-08-15 01:30 UTCEPSS rescore
  46. 2026-08-14 02:54 UTCEG score recompute
  47. 2026-08-14 02:54 UTCVendor advisory
  48. 2026-08-14 02:54 UTCGHSA enrichment
  49. 2026-08-13 22:00 UTCEPSS rescore
  50. 2026-08-13 01:39 UTCEG score recompute
  51. 2026-08-13 01:39 UTCVendor advisory
  52. 2026-08-13 01:39 UTCGHSA enrichment
  53. 2026-08-12 13:51 UTCEPSS rescore
  54. 2026-08-12 00:24 UTCEG score recompute
  55. 2026-08-12 00:24 UTCVendor advisory
  56. 2026-08-12 00:24 UTCGHSA enrichment
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-10 23:04 UTCVendor advisory
  59. 2026-08-10 23:04 UTCGHSA enrichment
  60. 2026-08-09 21:48 UTCEG score recompute
  61. 2026-08-09 21:48 UTCVendor advisory
  62. 2026-08-09 21:48 UTCGHSA enrichment
  63. 2026-08-09 13:46 UTCEPSS rescore
  64. 2026-08-08 20:33 UTCEG score recompute
  65. 2026-08-08 20:33 UTCVendor advisory
  66. 2026-08-08 20:33 UTCGHSA enrichment
  67. 2026-08-08 16:37 UTCEPSS rescore
  68. 2026-08-07 19:17 UTCVendor advisory
  69. 2026-08-07 19:17 UTCGHSA enrichment
  70. 2026-08-06 18:02 UTCEG score recompute
  71. 2026-08-06 18:02 UTCVendor advisory
  72. 2026-08-06 18:02 UTCGHSA enrichment
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-05 19:17 UTCEPSS rescore
  75. 2026-08-05 16:47 UTCEG score recompute

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53320?
CVE-2026-53320 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject zero bdoblocknr in nilfsioctlmarkblocks_dirty() nilfsioctlmarkblocksdirty() uses bd_oblocknr to detect dead blocks by comparing it with the current block number bd_blocknr. If they differ, the block is considered…
When was CVE-2026-53320 disclosed?
CVE-2026-53320 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53320 actively exploited?
CVE-2026-53320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53320?
CVE-2026-53320 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53320, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53320

Explore →

Is Your Infrastructure Affected by CVE-2026-53320?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs