CVE-2022-50313: erofs: fix order >= MAX_ORDER warning due to crafted negative i_size
In the Linux kernel, the following vulnerability has been resolved:
erofs: fix order >= MAX_ORDER warning due to crafted negative i_size
As syzbot reported [1], the root cause is that i_size field is a
signed type, and negative i_size is also less than EROFS_BLKSIZ.
As a consequence, it's handled as fast symlink unexpectedly.
Let's fall back to the generic path to deal with such unusual i_size.
[1] https://lore.kernel.org/r/000000000000ac8efa05e7feaa1f@google.com
Security readout for executives and security teams
Plain-English summary
CVE-2022-50313 is a Linux kernel EROFS filesystem bug triggered by a crafted negative file size. The public record describes an unexpected kernel warning path, not confirmed data theft or remote compromise. Business urgency is highest for systems that mount untrusted EROFS images or run affected kernel builds.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency based on current public evidence. Prioritize patching for infrastructure that handles filesystem images, container or embedded workflows, or user-supplied media. Track vendor advisories because severity and distribution impact are incomplete in the public CVE data.
Technical view
The Linux kernel EROFS code treated negative signed i_size values as less than EROFS_BLKSIZ, causing them to be handled as fast symlinks unexpectedly. The fix falls back to the generic path for unusual i_size values. The issue was reported by syzbot and fixed in referenced stable kernel commits.
Likely exposure
Exposure is likely limited to Linux systems with affected EROFS code paths, especially where crafted or untrusted EROFS filesystem images can be mounted or processed. The CVE record lists Linux kernel versions and stable commit references, but no distribution-specific package matrix is provided.
Exploitation context
No CISA KEV listing or cited source confirms active exploitation. The described trigger is a crafted negative i_size in EROFS metadata. Public sources characterize the result as a kernel warning condition, with no CVSS score or complete impact analysis provided.
Researcher notes
Key uncertainty is impact beyond the reported MAX_ORDER warning. The public description does not provide CVSS, CWE, exploitability details, or distro mappings. Analysis should focus on EROFS mount paths, crafted filesystem metadata handling, and whether downstream kernels have backported the referenced stable commits.
Mitigation direction
Update to a kernel or distribution package containing the referenced EROFS fix.
Check Linux distribution advisories for exact affected and fixed package versions.
Avoid mounting untrusted EROFS filesystem images until patched.
Where EROFS is unnecessary, follow vendor guidance to reduce or disable exposure.
Validation and detection
Inventory Linux kernels and identify systems with EROFS support enabled or available.
Compare running kernel builds against vendor advisories and referenced stable commits.
Review image-handling workflows for untrusted EROFS filesystem content.
Confirm patched systems include the EROFS negative i_size handling fix.
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-50313 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Sep 15, 2025, 14:46 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.