Skip to content
Noroxi
CVE-2026-45864· NVD / CVE Program· CNA Linux

fs/ntfs3: prevent infinite loops caused by the next valid being the same

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent infinite loops caused by the next valid being the same When processing valid within the range [valid : pos), if valid cannot be retrieved correctly, for example, if the retrieved valid value is always the same, this can trigger a potential infinite loop, similar to the hung problem reported by syzbot [1]. Adding a check for the valid value within the loop body, and terminating the loop and returning -EINVAL if the value is the same as the current value, can prevent this. [1] INFO: task syz.4.21:6056 blocked for more than 143 seconds. Call Trace: rwbase_write_lock+0x14f/0x750 kernel/locking/rwbase_rt.c:244 inode_lock include/linux/fs.h:1027 [inline] ntfs_file_write_iter+0xe6/0x870 fs/ntfs3/file.c:1284

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Jun 25, 2026
EPSS
0.2% · 5th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Affected systems

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15 and later · before 5.15.202
  • linux linux kernel5.16 and later · before 6.1.165
  • linux linux kernel6.2 and later · before 6.6.128
  • linux linux kernel6.7 and later · before 6.12.75
  • linux linux kernel6.13 and later · before 6.18.14
  • linux linux kernel6.19 and later · before 6.19.4

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

    • 5.15affected
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 50c822fcb36768f1fb356f05b02a2248ef81936daffected · git
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 6d93239b4fc479f7c0a412dd196ec0ca2672d14aaffected · git
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 71c8b966ec56e13c02388c1312910588bb49be7aaffected · git
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before b97e371e5d1c13d722335d46eb8bc1a22b272a0eaffected · git
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 4bf3bafb8e0635ed93e3cd4156dcbcc0fb960cb4affected · git
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before a47a2bb9aa6455d5cee1045814a60c749309c92baffected · git
    • 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 27b75ca4e51e3e4554dc85dbf1a0246c66106fd3affected · git
    • before 5.15not affected · semver
    • 5.15.202 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.18.14-16.18.14-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

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 Linux27b75ca4e51e3e4554dc85dbf1a0246c66106fd3Vendor (CNA)
Linux Linux4bf3bafb8e0635ed93e3cd4156dcbcc0fb960cb4Vendor (CNA)
Linux Linux50c822fcb36768f1fb356f05b02a2248ef81936dVendor (CNA)
Linux Linux6d93239b4fc479f7c0a412dd196ec0ca2672d14aVendor (CNA)
Linux Linux71c8b966ec56e13c02388c1312910588bb49be7aVendor (CNA)
Linux Linuxa47a2bb9aa6455d5cee1045814a60c749309c92bVendor (CNA)
Linux Linuxb97e371e5d1c13d722335d46eb8bc1a22b272a0eVendor (CNA)
debian:linux6.1.170-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.

  • CVE-2026-3144835 days apartext4: avoid infinite loops caused by residual data
    37Monitor
  • CVE-2026-5293328 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()
    31Monitor
  • CVE-2026-3155233 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom
    30Monitor
  • CVE-2026-6414853 days apartpds_core: fix error handling in pdsc_devcmd_wait
    30Monitor
  • CVE-2026-2345154 days apartbonding: prevent potential infinite loop in bond_header_parse()
    30Monitor
  • CVE-2026-459190 days apartsched/rt: Skip currently executing CPU in rto_next_cpu()
    22Monitor

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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

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

References

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

All records