Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-22036: exfat: fix random stack corruption after get_block

Noroxi assessment

Priority: Monitor (action score 28/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.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 1bb7ff4204b6d4927e982cd256286c09ed4fd8ca, 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2, f7447286363dc1e410bf30b87d75168f3519f9cc.

Low priority for now. Upgrade to Linux Linux 1bb7ff4204b6d4927e982cd256286c09ed4fd8ca, 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2, f7447286363dc1e410bf30b87d75168f3519f9cc 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: exfat: fix random stack corruption after get_block When get_block is called with a buffer_head allocated on the stack, such as do_mpage_readpage, stack corruption due to buffer_head UAF may occur in the following race condition situation. <CPU 0> <CPU 1> mpage_read_folio <<bh on stack>> do_mpage_readpage exfat_get_block bh_read __bh_read get_bh(bh) submit_bh wait_on_buffer ... end_buffer_read_sync __end_buffer_read_notouch unlock_buffer <<keep going>> ... ... ... ... <<bh is not valid out of mpage_read_folio>> . . another_function <<variable A on stack>> put_bh(bh) atomic_dec(bh->b_count) * stack corruption here * This patch returns -EAGAIN if a folio does not have buffers when bh_read needs to be called. By doing this, the caller can fallback to functions like block_read_full_folio(), create a buffer_head in the folio, and then call get_block again. Let's do not call bh_read() with on-stack buffer_head.

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Apr 16, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.0
CNA · Linux
7.8
0.8 point gap

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

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-2025-22036

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.

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 kernel6.8 and later · before 6.12.23
  • linux linux kernel6.13 and later · before 6.13.11
  • linux linux kernel6.14 and later · before 6.14.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

    • 6.8affected
    • 11a347fb6cef62ce47e84b97c45f2b2497c7593b and later · before 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2affected · git
    • 11a347fb6cef62ce47e84b97c45f2b2497c7593b and later · before f7447286363dc1e410bf30b87d75168f3519f9ccaffected · git
    • 11a347fb6cef62ce47e84b97c45f2b2497c7593b and later · before f807a6bf2005740fa26b4f59c4a003dc966b9afdaffected · git
    • 11a347fb6cef62ce47e84b97c45f2b2497c7593b and later · before 1bb7ff4204b6d4927e982cd256286c09ed4fd8caaffected · git
    • before 6.8not affected · semver
    • 6.12.23 and later · up to and including 6.12.*not affected · semver
    • 6.13.11 and later · up to and including 6.13.*not affected · semver
    • 6.14.2 and later · up to and including 6.14.*not affected · semver
    • 6.15 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.21.1.el10_06.12.0-55.21.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.21.1.el10_06.12.0-55.21.1.el10_0
Debian:13linuxbefore 6.12.25-16.12.25-1
Red Hat:enterprise_linux:10.0kernelbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64kbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-corebefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debugbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-corebefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-debuginfobefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-develbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-devel-matchedbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modulesbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-corebefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-extrabefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debuginfobefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-develbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-devel-matchedbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modulesbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-corebefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-extrabefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-abi-stablelistsbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-corebefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debugbefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debug-corebefore 0:6.12.0-55.21.1.el10_00:6.12.0-55.21.1.el10_0

+71

Same product

linux: all records

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-2025-22034Apr 16, 2025 · mm/gup: reject FOLL_SPLIT_PMD with hugetlb VMAs
    22Monitor
  • ← EarlierCVE-2025-22035Apr 16, 2025 · tracing: Fix use-after-free in print_graph_function_flags during tracer switching
    31Monitor
  • Later →CVE-2025-22038Apr 16, 2025 · ksmbd: validate zero num_subauth before sub_auth is accessed
    28Monitor

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 Linux1bb7ff4204b6d4927e982cd256286c09ed4fd8caVendor (CNA)
Linux Linux49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2Vendor (CNA)
Linux Linuxf7447286363dc1e410bf30b87d75168f3519f9ccVendor (CNA)
Linux Linuxf807a6bf2005740fa26b4f59c4a003dc966b9afdVendor (CNA)
almalinux:kernel-abi-stablelists6.12.0-55.21.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.21.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.25-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-55.21.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
rocky linux:kernel0:6.12.0-55.21.1.el10_0 · Rocky Linux:10Package 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.

No history yet (it accumulates with the daily EPSS job).

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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

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
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records