CVE record · CVE-2022-49169

f2fs: use spin_lock to avoid hang

No CVSS scoreEPSS 0.0026 · 18th percentile

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 01:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Linux Linux
  • affected 66af62ce7588736ae65edfdb1c0df597775c4d21 to before 2eff60346e7ae1a24cd868b8fdcf58e946e7dde1 git
  • affected 66af62ce7588736ae65edfdb1c0df597775c4d21 to before 738886004bd2885ac2db0bc63b4874aa471ca87e git
  • affected 66af62ce7588736ae65edfdb1c0df597775c4d21 to before ec4187d45cc1c2d69fffeee5fa6aa4cb62477cfb git
  • affected 66af62ce7588736ae65edfdb1c0df597775c4d21 to before 98237fcda4a24e67b0a4498c17d5aa4ad4537bc7 git
Other versions: unaffected
Linux Linux
  • affected 3.8
  • unaffected before 3.8 semver
  • unaffected 5.15.33 to 5.15.*, inclusive semver
  • unaffected 5.16.19 to 5.16.*, inclusive semver
  • unaffected 5.17.2 to 5.17.*, inclusive semver
  • unaffected 5.18 to *, inclusive original_commit_for_fix
Other versions: affected
Identifiers
CVE-2022-49169
CNA
Linux
Published
26 Feb 2025
Updated
12 Aug 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.0026, the 18th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 26 Feb 2025. New records show when each source confirmed them.

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.