LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22076: exfat: fix missing shutdown check

In the Linux kernel, the following vulnerability has been resolved: exfat: fix missing shutdown check xfstests generic/730 test failed because after deleting the device that still had dirty data, the file could still be read without returning an error. The reason is the missing shutdown check in ->read_iter. I also noticed that shutdown checks were missing from ->write_iter, ->splice_read, and ->mmap. This commit adds shutdown checks to all of them.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux kernel exFAT filesystem bug allowed file operations to continue after an underlying device shutdown or removal instead of returning an error. This can weaken data-integrity signals on systems using exFAT storage. Public sources do not provide CVSS scoring or evidence of active exploitation.

Executive priority

Treat this as a targeted kernel maintenance issue rather than an emergency. Prioritize patch validation where exFAT is used operationally or with removable media. Urgency is limited by missing severity, CVSS, and exploitation evidence in the supplied sources.

Technical view

The exFAT implementation missed shutdown checks in read_iter and also lacked them in write_iter, splice_read, and mmap. The reported failure occurred when a device with dirty data was deleted and data could still be read. Stable kernel commits add shutdown checks to those file-operation paths.

Likely exposure

Linux systems using exFAT mounts are the relevant exposure, especially removable, hot-unplugged, or virtual storage. Exposure depends on kernel version and distribution backports. The supplied record identifies Linux kernel affected version data and stable commits, but not downstream package names.

Exploitation context

The bundle does not show KEV listing, public exploitation, exploit maturity, or attacker prerequisites. The evidence describes a filesystem correctness and error-handling flaw found through xfstests, not a demonstrated real-world intrusion path.

Researcher notes

The public record is sparse. It confirms missing shutdown checks and upstream stable commits, but does not establish confidentiality impact, privilege requirements, exploitability, or downstream fixed package versions. Further assessment should focus on kernel provenance and whether exFAT is reachable in production workflows.

Mitigation direction

  • Check Linux vendor advisories for backported fixes for CVE-2025-22076.
  • Update to a kernel build containing the referenced stable exFAT shutdown-check commits.
  • Prioritize systems that mount exFAT removable, virtual, or externally managed storage.
  • Avoid relying on exFAT devices after removal, shutdown, or storage-layer errors.

Validation and detection

  • Inventory Linux kernel versions and confirm whether vendor packages include the stable fixes.
  • Identify systems with exFAT support enabled or active exFAT mounts.
  • Review storage logs for device removal, shutdown, or I/O error events involving exFAT.
  • Confirm patch status using distribution security metadata, not only upstream version numbers.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22076 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf761fcdd289d07e8547fef7ac76c3760fc7803f2, f761fcdd289d07e8547fef7ac76c3760fc7803f2, f761fcdd289d07e8547fef7ac76c3760fc7803f2, f761fcdd289d07e8547fef7ac76c3760fc7803f2unaffected
LinuxLinux6.12, 0, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.