Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53388: fuse: re-lock request before replacing page cache folio

Noroxi assessment

Priority: Monitor (action score 31/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.13% (FIRST EPSS).
  • 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.
  • Fixed version: Linux Linux 0223f452532d9cd8a5e87c45de828fd93c99bd25, 030fe3e9d8abdee303dd7e9e42f45082d382a407, 46473ddccdc5065033e397d6e62c280dbcd3d9c2; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0223f452532d9cd8a5e87c45de828fd93c99bd25, 030fe3e9d8abdee303dd7e9e42f45082d382a407, 46473ddccdc5065033e397d6e62c280dbcd3d9c2; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 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: fuse: re-lock request before replacing page cache folio fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free the fuse_io_args (eg fuse_readpages_end()) while the subsequent copy chain logic after fuse_try_move_folio() accesses the fuse_io_args, leading to use-after-free issues. Fix this by calling lock_request() before replace_page_cache_folio(). This ensures the request is locked on the success path which will prevent the fuse_io_args from being freed while the later copying logic runs, and also ensures that the ap->folios[i]->mapping is never null since ap->folios[i] will always point to the newfolio after replace_page_cache_folio().

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2026-53388

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.

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.

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 kernel2.6.35 and later · before 5.15.211
  • linux linux kernel5.16 and later · before 6.1.177
  • linux linux kernel6.2 and later · before 6.6.144
  • linux linux kernel6.7 and later · before 6.12.95
  • linux linux kernel6.13 and later · before 6.18.37
  • linux linux kernel6.19 and later · before 7.0.14
  • linux linux kernel7.1 and later · before 7.1.2

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.35affected
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before 7c18691e0cfda29672f79bafde8abdb7710674f6affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before 5927b43a4f8d89e86930f524bf63e9c7e66f61b4affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before 030fe3e9d8abdee303dd7e9e42f45082d382a407affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before 46473ddccdc5065033e397d6e62c280dbcd3d9c2affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before af2892249d982a1c036ca456cc135374e68b6677affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before 0223f452532d9cd8a5e87c45de828fd93c99bd25affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before e28db6ac4792d065ab32565fd9f0a2361c3d4666affected · git
    • ce534fb052928ce556639d7ecf01cbf4e01321e1 and later · before a078484921052d0badd827fcc2770b5cfc1d4120affected · git
    • before 2.6.35not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.69.1.el10_26.12.0-211.69.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2026-53384Jul 19, 2026 · serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
    39Monitor
  • ← EarlierCVE-2026-53385Jul 19, 2026 · vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write
    22Monitor
  • Later →CVE-2026-53391Jul 19, 2026 · NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr
    30Monitor

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 Linux0223f452532d9cd8a5e87c45de828fd93c99bd25Vendor (CNA)
Linux Linux030fe3e9d8abdee303dd7e9e42f45082d382a407Vendor (CNA)
Linux Linux46473ddccdc5065033e397d6e62c280dbcd3d9c2Vendor (CNA)
Linux Linux5927b43a4f8d89e86930f524bf63e9c7e66f61b4Vendor (CNA)
Linux Linux7c18691e0cfda29672f79bafde8abdb7710674f6Vendor (CNA)
Linux Linuxa078484921052d0badd827fcc2770b5cfc1d4120Vendor (CNA)
Linux Linuxaf2892249d982a1c036ca456cc135374e68b6677Vendor (CNA)
Linux Linuxe28db6ac4792d065ab32565fd9f0a2361c3d4666Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.178.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.178.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.178.1.rt7.519.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.177-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.1.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
rocky linux:kernel0:4.18.0-553.178.1.el8_10 · Rocky Linux:8Package registry (OSV)
rocky linux:kernel-rt0:4.18.0-553.178.1.rt7.519.el8_10 · Rocky Linux:8Package registry (OSV)
suse:kernel-64kb5.14.21-150400.24.240.2 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-default5.14.21-150400.24.240.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-default-base5.14.21-150400.24.240.2.150400.24.120.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-docs5.14.21-150400.24.240.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP4_Update_591-150400.9.5.1 · SUSE:Linux Enterprise Live Patching 15 SP4Package registry (OSV)

+7

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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records