LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48665: exfat: fix overflow for large capacity partition

In the Linux kernel, the following vulnerability has been resolved: exfat: fix overflow for large capacity partition Using int type for sector index, there will be overflow in a large capacity partition. For example, if storage with sector size of 512 bytes and partition capacity is larger than 2TB, there will be overflow.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects exFAT handling on very large partitions. A sector index stored in an int can overflow when partition capacity exceeds about 2TB with 512-byte sectors. The sources do not state real-world impact, exploitation, or severity, so urgency depends on whether systems mount large or untrusted exFAT media.

Executive priority

Track for kernel patching and prioritize exposed endpoints or storage workflows. This is not confirmed as actively exploited, but filesystem bugs can affect reliability and data handling when untrusted media is mounted.

Technical view

The Linux exFAT filesystem code used an int for sector indexing, creating an overflow condition on large-capacity partitions. The provided example is 512-byte sectors with capacity above 2TB. Stable kernel commits are referenced as the resolution, but the bundle does not describe crash, corruption, privilege, or code-execution impact.

Likely exposure

Most exposure is on Linux systems that mount exFAT filesystems, especially removable drives or storage images above 2TB. The affected version data lists Linux kernel 5.19, 5.19.12, and 6.0 entries, but detailed range semantics are incomplete in the bundle.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The bundle does not provide exploitability details. Treat untrusted exFAT media as the most relevant scenario, but do not assume exploitation without vendor or threat-intelligence confirmation.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. The root issue is integer overflow in exFAT sector indexing for large partitions. Impact class, CVSS, CWE, and exploitation status are not provided, so validation should focus on affected kernel lineage and exFAT attack surface.

Mitigation direction

  • Check your Linux distributor or kernel vendor advisory for fixed builds.
  • Upgrade kernels to versions containing the referenced stable exFAT fix commits.
  • Reduce or disable auto-mounting of untrusted exFAT removable media.
  • Prioritize systems handling large exFAT volumes or storage images above 2TB.
  • Document any temporary media-handling restrictions for operations teams.

Validation and detection

  • Inventory Linux kernel versions across systems that mount exFAT filesystems.
  • Identify servers, workstations, and appliances using large exFAT partitions.
  • Confirm installed kernels include the referenced stable commits or vendor backports.
  • Review removable-media and storage-image handling policies for untrusted exFAT content.
  • Monitor vendor advisories for clarified affected ranges and impact.
Prepared
Confidence
medium
Sources
4

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-2022-48665 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
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1b6138385499507147e8f654840f4c39afe6adbf, 1b6138385499507147e8f654840f4c39afe6adbfunaffected
LinuxLinux5.19, 0, 5.19.12, 6.0affected
Weakness

CWE details

No CWE listed

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