LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50013: f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page() As Dipanjan Das <mail.dipanjan.das@gmail.com> reported, syzkaller found a f2fs bug as below: RIP: 0010:f2fs_new_node_page+0x19ac/0x1fc0 fs/f2fs/node.c:1295 Call Trace: write_all_xattrs fs/f2fs/xattr.c:487 [inline] __f2fs_setxattr+0xe76/0x2e10 fs/f2fs/xattr.c:743 f2fs_setxattr+0x233/0xab0 fs/f2fs/xattr.c:790 f2fs_xattr_generic_set+0x133/0x170 fs/f2fs/xattr.c:86 __vfs_setxattr+0x115/0x180 fs/xattr.c:182 __vfs_setxattr_noperm+0x125/0x5f0 fs/xattr.c:216 __vfs_setxattr_locked+0x1cf/0x260 fs/xattr.c:277 vfs_setxattr+0x13f/0x330 fs/xattr.c:303 setxattr+0x146/0x160 fs/xattr.c:611 path_setxattr+0x1a7/0x1d0 fs/xattr.c:630 __do_sys_lsetxattr fs/xattr.c:653 [inline] __se_sys_lsetxattr fs/xattr.c:649 [inline] __x64_sys_lsetxattr+0xbd/0x150 fs/xattr.c:649 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 NAT entry and nat bitmap can be inconsistent, e.g. one nid is free in nat bitmap, and blkaddr in its NAT entry is not NULL_ADDR, it may trigger BUG_ON() in f2fs_new_node_page(), fix it.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel F2FS filesystem bug that can hit a kernel BUG condition when internal node allocation metadata becomes inconsistent. The available sources do not provide CVSS, confirmed exploit activity, or a broader confidentiality impact. The clearest business risk is system availability on Linux hosts that use F2FS.

Executive priority

Treat as a targeted Linux availability risk, not a confirmed widespread emergency. Prioritize remediation where F2FS is used in production, appliances, or storage workflows, and handle through normal kernel patch governance unless vendor guidance raises severity.

Technical view

The fix avoids f2fs_bug_on() in f2fs_new_node_page() when a NAT bitmap marks a node ID free while its NAT entry still has a non-NULL block address. The reported call trace reaches the issue through F2FS extended-attribute handling. Impact is not fully characterized in the sources.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds where F2FS is in use or can process F2FS filesystems. Systems without F2FS usage are less likely to be practically exposed. Downstream distribution status must be mapped separately.

Exploitation context

The source says syzkaller found the bug. CISA KEV status is false in the bundle, and no provided source states active exploitation, public exploit availability, remote reachability, or privilege requirements.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed affected range semantics are provided. The core condition is an F2FS NAT consistency issue that previously reached f2fs_bug_on() in node page allocation.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-50013 status.
  • Update to a kernel containing the referenced F2FS stable fixes.
  • Prioritize hosts that mount or accept F2FS filesystems.
  • Limit untrusted access to F2FS-backed storage where practical.
  • Track downstream distribution backports, not only upstream version numbers.

Validation and detection

  • Inventory Linux systems and identify F2FS usage.
  • Map running kernel builds to vendor advisories or stable fix commits.
  • Review kernel logs for F2FS BUG/Oops events around xattr operations.
  • Confirm patched kernels include the relevant stable commit for their branch.
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-50013 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, 4.19.256, 5.4.211, 5.10.138, 5.15.63, 5.19.4, 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.