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-49318f2fs: remove WARN_ON in f2fs_is_valid_blkaddr

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and __is_bitmap_valid. For example, in f2fs_is_valid_blkaddr, if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ, it invokes WARN_ON if blkaddr is not in the right range. The call trace is as follows: f2fs_get_node_info+0x45f/0x1070 read_node_page+0x577/0x1190 __get_node_page.part.0+0x9e/0x10e0 __get_node_page f2fs_get_node_page+0x109/0x180 do_read_inode f2fs_iget+0x2a5/0x58b0 f2fs_fill_super+0x3b39/0x7ca0 Fix these two WARNs by replacing WARN_ON with dump_stack.

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-49318, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.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 (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 c9b60788fc760d136211853f10ce73dc152d1f4a – < 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd
    • affected c9b60788fc760d136211853f10ce73dc152d1f4a – < 32bea51fe4c6e92c00403739f7547c89219bea88
    • affected c9b60788fc760d136211853f10ce73dc152d1f4a – < 99c09b298e47ebbe345a6da9f268b32a6b0f4582
    • affected c9b60788fc760d136211853f10ce73dc152d1f4a – < cd6374af36cc548464d8c47a93fdba7303bb82a4
    • affected c9b60788fc760d136211853f10ce73dc152d1f4a – < 8c62c5e26345c34d199b4b8c8e69255ba3d0e751
    • affected c9b60788fc760d136211853f10ce73dc152d1f4a – < dc2f78e2d4cc844a1458653d57ce1b54d4a29f21
    • affected bdffda8db8d9e0125b9a41edc420c39f9905c6ab
    • affected aafb371575161e315a98dee978b72f9d5357791b
    • affected ad19d1e78fd51f5b4bf3ebbcbf3a133c8c03c49d
    • affected 4.4.172 – < 4.5
    • affected 4.9.144 – < 4.10
    • affected 4.14.86 – < 4.15
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.122 – ≤ 5.10.*
    • unaffected 5.15.47 – ≤ 5.15.*
    • unaffected 5.17.15 – ≤ 5.17.*
    • unaffected 5.18.4 – ≤ 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-49318 badge
[![CVE-2022-49318](https://cveledger.app/badge/CVE-2022-49318.svg)](https://cveledger.app/cve/CVE-2022-49318)

Record last updated .