LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49363: f2fs: fix to do sanity check on block address in f2fs_do_zero_range()

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on block address in f2fs_do_zero_range() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215894 I have encountered a bug in F2FS file system in kernel v5.17. I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: kernel BUG at fs/f2fs/segment.c:2291! Call Trace: f2fs_invalidate_blocks+0x193/0x2d0 f2fs_fallocate+0x2593/0x4a70 vfs_fallocate+0x2a5/0xac0 ksys_fallocate+0x35/0x70 __x64_sys_fallocate+0x8e/0xf0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr. Let's fix the issue by adding sanity check on block address before updating SIT table with it.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49363 is a Linux kernel F2FS bug where corrupted filesystem metadata can make the kernel panic during file allocation. The public record does not provide CVSS, KEV listing, or active exploitation evidence, so business urgency depends on whether affected systems use F2FS or process untrusted F2FS images.

Executive priority

Treat this as targeted kernel reliability risk, not confirmed active exploitation. Patch during normal kernel maintenance unless F2FS is used in production, on exposed removable-media workflows, or on fleets where kernel panics create material availability impact.

Technical view

The issue is in f2fs_do_zero_range()/f2fs_fallocate(): inconsistent inode block mapping and SIT table data from a fuzzed F2FS image can lead to f2fs_invalidate_blocks() updating the SIT with an invalid block address, triggering a kernel BUG. The fix adds a block-address sanity check before the SIT update.

Likely exposure

Exposure is most relevant to Linux systems using the F2FS filesystem on affected kernel lines or handling malformed F2FS images. The bundle lists Linux kernel versions around 3.8 through 5.19 and stable fixes, but does not map distributions, device models, or package names.

Exploitation context

The cited evidence describes a fuzzing-discovered kernel panic using a malformed F2FS image. KEV is false, and the provided sources do not claim active exploitation, public weaponization, privilege escalation, or remote exploitability.

Researcher notes

Evidence is limited to the CVE description and kernel stable commits. The root cause and fix direction are clear, but severity scoring, affected distro packages, exploit maturity, and impact beyond denial of service are not established in the supplied sources.

Mitigation direction

  • Apply kernel updates containing the referenced upstream stable fixes.
  • Follow Linux distribution or device vendor guidance for backported fixed kernels.
  • Prioritize systems that use F2FS or process removable/untrusted F2FS media.
  • Limit handling of untrusted F2FS images where operationally feasible until patched.

Validation and detection

  • Inventory kernels and identify systems using F2FS filesystems.
  • Confirm installed kernel packages include the relevant stable fix commits or vendor backports.
  • Review crash telemetry for F2FS-related kernel BUG or panic events.
  • Track vendor advisories because the bundle lacks distro-specific fixed versions.
Prepared
Confidence
medium
Sources
8

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-49363 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
7Source 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
LinuxLinux98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4unaffected
LinuxLinux3.8, 0, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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