Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49380f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215897 I have encountered a bug in F2FS file system in kernel v5.17. The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: The kernel message is shown below: kernel BUG at fs/f2fs/f2fs.h:2511! Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed to zero, then once dec_valid_node_count() was called, it will cause BUG_ON(), this patch fixes to print warning info and set SBI_NEED_FSCK into CP instead of panic.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49380, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < f8b3c3fcf33105bc1ee7788e3b51b0a1ae42ae53
    • affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < 2766ddaf45b69252bb8fe526b5b6e56904a9ae7a
    • affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < bce859358d3d5940aa858e40ceee70ee6e76130e
    • affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < 89d9a48d0cd30429463ea4e37ca83be6773ed5eb
    • affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < ccffa99ae6a1f44797b57444c6a80382a42928fe
    • affected 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 – < 4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.121 – ≤ 5.10.*
    • unaffected 5.15.46 – ≤ 5.15.*
    • unaffected 5.17.14 – ≤ 5.17.*
    • unaffected 5.18.3 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49380 badge
[![CVE-2022-49380](https://cveledger.app/badge/CVE-2022-49380.svg)](https://cveledger.app/cve/CVE-2022-49380)

Record last updated .