Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49425

f2fs: fix dereference of stale list iterator after loop body

High7.8EPSS 0.28%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix dereference of stale list iterator after loop body The list iterator variable will be a bogus pointer if no break was hit. Dereferencing it (cur->page in this case) could load an out-of-bounds/undefined value making it unsafe to use that in the comparision to determine if the specific element was found. Since 'cur->page' *can* be out-ouf-bounds it cannot be guaranteed that by chance (or intention of an attacker) it matches the value of 'page' even though the correct element was not found. This is fixed by using a separate list iterator variable for the loop and only setting the original variable if a suitable element was found. Then determing if the element was found is simply checking if the variable is set.

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-49425, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.28% · top 80% of all CVEs (7 Nov 2026)
Loading the EPSS history…

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

Weakness

Affected products

  • Linux · Linux

    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < 385edd3ce5b4b1e9d31f474a5e35a39779ec1110
    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < 5e47a7add3dda7f236548c5ec3017776dc2a729f
    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < 51d584704d18e60fa473823654f35611c777b291
    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < 45b2b7d7108ae1e25a5036cab04ab9273e792332
    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < b26e1c777890e4b938136deb8ec07a29f33862e4
    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < ed7efc472c00986dcd6903ab6ed165c7fa167674
    • affected 8c242db9b8c01b252290e23827163787f07e01d1 – < 2aaf51dd39afb6d01d13f1e6fe20b684733b37d5
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 4.19.247 – ≤ 4.19.*
    • 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 (7)

Sources

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

Badge for a README or a ticket

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

Record last updated .