CVE-2022-49464: erofs: fix buffer copy overflow of ztailpacking feature
In the Linux kernel, the following vulnerability has been resolved:
erofs: fix buffer copy overflow of ztailpacking feature
I got some KASAN report as below:
[ 46.959738] ==================================================================
[ 46.960430] BUG: KASAN: use-after-free in z_erofs_shifted_transform+0x2bd/0x370
[ 46.960430] Read of size 4074 at addr ffff8880300c2f8e by task fssum/188
...
[ 46.960430] Call Trace:
[ 46.960430] <TASK>
[ 46.960430] dump_stack_lvl+0x41/0x5e
[ 46.960430] print_report.cold+0xb2/0x6b7
[ 46.960430] ? z_erofs_shifted_transform+0x2bd/0x370
[ 46.960430] kasan_report+0x8a/0x140
[ 46.960430] ? z_erofs_shifted_transform+0x2bd/0x370
[ 46.960430] kasan_check_range+0x14d/0x1d0
[ 46.960430] memcpy+0x20/0x60
[ 46.960430] z_erofs_shifted_transform+0x2bd/0x370
[ 46.960430] z_erofs_decompress_pcluster+0xaae/0x1080
The root cause is that the tail pcluster won't be a complete filesystem
block anymore. So if ztailpacking is used, the second part of an
uncompressed tail pcluster may not be ``rq->pageofs_out``.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49464 is a Linux kernel memory-safety flaw in EROFS, a read-only filesystem. A local, low-privileged actor could potentially trigger serious confidentiality, integrity, and availability impacts if an affected kernel processes the vulnerable EROFS ztailpacking path.
Executive priority
Treat as high priority for Linux fleets using affected kernels, especially multi-user or workload-hosting systems. Prioritize normal kernel patch cycles unless vendor guidance or local exposure indicates emergency handling.
Technical view
The issue is a use-after-free/buffer copy overflow in z_erofs_shifted_transform during EROFS decompression for ztailpacking. The CVE cites a KASAN report showing memcpy reading freed memory. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions or backports with the vulnerable EROFS ztailpacking implementation. The source bundle does not prove exposure for every distribution kernel; vendor backport status must be checked.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not report active exploitation. The CVSS vector indicates local, low-privileged exploitation conditions without user interaction, but the sources do not provide validated exploit details.
Researcher notes
Evidence supports a kernel memory safety issue in EROFS ztailpacking with severe local impact. The provided data is incomplete on distribution-specific affected ranges, exploitability in default configurations, and operational mitigations beyond applying kernel fixes.
Mitigation direction
Update affected Linux kernels using vendor or stable kernel guidance.
Confirm the referenced stable fixes are present or backported.
Restrict local users or workloads that can trigger EROFS processing where feasible.
Avoid relying on version strings alone; verify vendor patch status.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, containers, and appliances.
Check whether EROFS support is enabled or used in relevant environments.
Map installed kernels against vendor advisories and stable fix commits.
Review kernel crash, KASAN, or filesystem error logs for related EROFS failures.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.