CVE-2022-49318: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd, 32bea51fe4c6e92c00403739f7547c89219bea88, 4.10.
Low priority for now. Upgrade to Linux Linux 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd, 32bea51fe4c6e92c00403739f7547c89219bea88, 4.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 26, 2025
- Updated
- Aug 15, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.4.198
- linux linux kernel5.5 and later · before 5.10.122
- linux linux kernel5.11 and later · before 5.15.47
- linux linux kernel5.16 and later · before 5.17.15
- linux linux kernel5.18 and later · before 5.18.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- bdffda8db8d9e0125b9a41edc420c39f9905c6ab, aafb371575161e315a98dee978b72f9d5357791b, ad19d1e78fd51f5b4bf3ebbcbf3a133c8c03c49d, 4.19affected
- c9b60788fc760d136211853f10ce73dc152d1f4a and later · before 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fdaffected · git
- c9b60788fc760d136211853f10ce73dc152d1f4a and later · before 32bea51fe4c6e92c00403739f7547c89219bea88affected · git
- c9b60788fc760d136211853f10ce73dc152d1f4a and later · before 99c09b298e47ebbe345a6da9f268b32a6b0f4582affected · git
- c9b60788fc760d136211853f10ce73dc152d1f4a and later · before cd6374af36cc548464d8c47a93fdba7303bb82a4affected · git
- c9b60788fc760d136211853f10ce73dc152d1f4a and later · before 8c62c5e26345c34d199b4b8c8e69255ba3d0e751affected · git
- c9b60788fc760d136211853f10ce73dc152d1f4a and later · before dc2f78e2d4cc844a1458653d57ce1b54d4a29f21affected · git
- 4.4.172 and later · before 4.5affected · semver
- 4.9.144 and later · before 4.10affected · semver
- 4.14.86 and later · before 4.15affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.18.5-1 | 5.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49316Feb 26, 2025 · NFSv4: Don't hold the layoutget locks across multiple RPC calls22Monitor
- ← EarlierCVE-2022-49317Feb 26, 2025 · f2fs: avoid infinite loop to flush node pages22Monitor
- Later →CVE-2022-49319Feb 26, 2025 · iommu/arm-smmu-v3: check return value after calling platform_get_resource()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd | Vendor (CNA) |
| Linux Linux | 32bea51fe4c6e92c00403739f7547c89219bea88 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 8c62c5e26345c34d199b4b8c8e69255ba3d0e751 | Vendor (CNA) |
| Linux Linux | 99c09b298e47ebbe345a6da9f268b32a6b0f4582 | Vendor (CNA) |
| Linux Linux | cd6374af36cc548464d8c47a93fdba7303bb82a4 | Vendor (CNA) |
| Linux Linux | dc2f78e2d4cc844a1458653d57ce1b54d4a29f21 | Vendor (CNA) |
| debian:linux | 5.18.5-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/32bea51fe4c6e92c00403739f7547c89219bea88
- git.kernel.org/stable/c/8c62c5e26345c34d199b4b8c8e69255ba3d0e751
- git.kernel.org/stable/c/99c09b298e47ebbe345a6da9f268b32a6b0f4582
- git.kernel.org/stable/c/cd6374af36cc548464d8c47a93fdba7303bb82a4
- git.kernel.org/stable/c/dc2f78e2d4cc844a1458653d57ce1b54d4a29f21
Vendor advisories and official records. Exploit/PoC links are deliberately left out.