Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53845: nilfs2: fix infinite loop in nilfs_mdt_get_block()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Fixed version: Linux Linux 25457d07c8146e57d28906c663def033dc425af6, 34c5f17222b50c79848bb03ec8811648813e6a45, 5b29661669cb65b9750a3cf70ed3eaf947b92167.

Low priority for now. Upgrade to Linux Linux 25457d07c8146e57d28906c663def033dc425af6, 34c5f17222b50c79848bb03ec8811648813e6a45, 5b29661669cb65b9750a3cf70ed3eaf947b92167 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix infinite loop in nilfs_mdt_get_block() If the disk image that nilfs2 mounts is corrupted and a virtual block address obtained by block lookup for a metadata file is invalid, nilfs_bmap_lookup_at_level() may return the same internal return code as -ENOENT, meaning the block does not exist in the metadata file. This duplication of return codes confuses nilfs_mdt_get_block(), causing it to read and create a metadata block indefinitely. In particular, if this happens to the inode metadata file, ifile, semaphore i_rwsem can be left held, causing task hangs in lock_mount. Fix this issue by making nilfs_bmap_lookup_at_level() treat virtual block address translation failures with -ENOENT as metadata corruption instead of returning the error code.

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53845

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.30affected
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before cfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before d536f9976bb04e9c84cf80045a9355975e418f41affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before fe1cbbcb1a2532ee1654e1ff121be8906d83c6f0affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before 8a89d36a07afe1ed4564df51fefa2bb556c85412affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before 8d07d9119642ba43d21f8ba64d51d01931096b20affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before 25457d07c8146e57d28906c663def033dc425af6affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before 34c5f17222b50c79848bb03ec8811648813e6a45affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before 5b29661669cb65b9750a3cf70ed3eaf947b92167affected · git
    • bdb265eae08db578e7cf5739be16f389d495fc75 and later · before a6a491c048882e7e424d407d32cba0b52d9ef2bfaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-53843Dec 9, 2025 · net: openvswitch: reject negative ifindex
    0Monitor
  • ← EarlierCVE-2023-53844Dec 9, 2025 · drm/ttm: Don't leak a resource on swapout move error
    31Monitor
  • Later →CVE-2023-53846Dec 9, 2025 · f2fs: fix to do sanity check on direct node in truncate_dnode()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux25457d07c8146e57d28906c663def033dc425af6Vendor (CNA)
Linux Linux34c5f17222b50c79848bb03ec8811648813e6a45Vendor (CNA)
Linux Linux5b29661669cb65b9750a3cf70ed3eaf947b92167Vendor (CNA)
Linux Linux8a89d36a07afe1ed4564df51fefa2bb556c85412Vendor (CNA)
Linux Linux8d07d9119642ba43d21f8ba64d51d01931096b20Vendor (CNA)
Linux Linuxa6a491c048882e7e424d407d32cba0b52d9ef2bfVendor (CNA)
Linux Linuxcfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2Vendor (CNA)
Linux Linuxd536f9976bb04e9c84cf80045a9355975e418f41Vendor (CNA)
Linux Linuxfe1cbbcb1a2532ee1654e1ff121be8906d83c6f0Vendor (CNA)
debian:linux6.1.37-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records