CVE-2022-50753: f2fs: fix to do sanity check on summary info
Noroxi assessment
Priority: Monitor (action score 31/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.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0922ad64ccefa3e483e84355942b86e13c8fea68, 4a8e8bf280703e04e0b9d91f101e1fdd9a5bd09e, 73687c53919f49dff3852155621dab7a35c52854.
Low priority for now. Upgrade to Linux Linux 0922ad64ccefa3e483e84355942b86e13c8fea68, 4a8e8bf280703e04e0b9d91f101e1fdd9a5bd09e, 73687c53919f49dff3852155621dab7a35c52854 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: fix to do sanity check on summary info As Wenqing Liu reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=216456 BUG: KASAN: use-after-free in recover_data+0x63ae/0x6ae0 [f2fs] Read of size 4 at addr ffff8881464dcd80 by task mount/1013 CPU: 3 PID: 1013 Comm: mount Tainted: G W 6.0.0-rc4 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x45/0x5e print_report.cold+0xf3/0x68d kasan_report+0xa8/0x130 recover_data+0x63ae/0x6ae0 [f2fs] f2fs_recover_fsync_data+0x120d/0x1fc0 [f2fs] f2fs_fill_super+0x4665/0x61e0 [f2fs] mount_bdev+0x2cf/0x3b0 legacy_get_tree+0xed/0x1d0 vfs_get_tree+0x81/0x2b0 path_mount+0x47e/0x19d0 do_mount+0xce/0xf0 __x64_sys_mount+0x12c/0x1a0 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd The root cause is: in fuzzed image, SSA table is corrupted: ofs_in_node is larger than ADDRS_PER_PAGE(), result in out-of-range access on 4k-size page. - recover_data - do_recover_data - check_index_in_prev_nodes - f2fs_data_blkaddr This patch adds sanity check on summary info in recovery and GC flow in where the flows rely on them. After patch: [ 29.310883] F2FS-fs (loop0): Inconsistent ofs_in_node:65286 in summary, ino:0, nid:6, max:1018
- Published
- Dec 24, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
—
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
- 3.11affected
- b292dcab068e141d8a820b77cbcc88d98c610eb4 and later · before c99860f9a75079f339ed7670425b1ac58f26e2ffaffected · git
- b292dcab068e141d8a820b77cbcc88d98c610eb4 and later · before 4a8e8bf280703e04e0b9d91f101e1fdd9a5bd09eaffected · git
- b292dcab068e141d8a820b77cbcc88d98c610eb4 and later · before 73687c53919f49dff3852155621dab7a35c52854affected · git
- b292dcab068e141d8a820b77cbcc88d98c610eb4 and later · before e168f819bfa42459b14f479e55ebd550bcc78899affected · git
- b292dcab068e141d8a820b77cbcc88d98c610eb4 and later · before 0922ad64ccefa3e483e84355942b86e13c8fea68affected · git
- b292dcab068e141d8a820b77cbcc88d98c610eb4 and later · before c6ad7fd16657ebd34a87a97d9588195aae87597daffected · git
- before 3.11not affected · semver
- 5.4.220 and later · up to and including 5.4.*not affected · semver
- 5.10.150 and later · up to and including 5.10.*not affected · 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 6.0.3-1 | 6.0.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50751Dec 24, 2025 · configfs: fix possible memory leak in configfs_create_dir()0Monitor
- ← EarlierCVE-2022-50752Dec 24, 2025 · md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk()31Monitor
- Later →CVE-2022-50754Dec 24, 2025 · apparmor: fix a memleak in multi_transaction_new()0Monitor
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 | 0922ad64ccefa3e483e84355942b86e13c8fea68 | Vendor (CNA) |
| Linux Linux | 4a8e8bf280703e04e0b9d91f101e1fdd9a5bd09e | Vendor (CNA) |
| Linux Linux | 73687c53919f49dff3852155621dab7a35c52854 | Vendor (CNA) |
| Linux Linux | c6ad7fd16657ebd34a87a97d9588195aae87597d | Vendor (CNA) |
| Linux Linux | c99860f9a75079f339ed7670425b1ac58f26e2ff | Vendor (CNA) |
| Linux Linux | e168f819bfa42459b14f479e55ebd550bcc78899 | Vendor (CNA) |
| debian:linux | 6.0.3-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.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
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/4a8e8bf280703e04e0b9d91f101e1fdd9a5bd09e
- git.kernel.org/stable/c/73687c53919f49dff3852155621dab7a35c52854
- git.kernel.org/stable/c/c6ad7fd16657ebd34a87a97d9588195aae87597d
- git.kernel.org/stable/c/c99860f9a75079f339ed7670425b1ac58f26e2ff
- git.kernel.org/stable/c/e168f819bfa42459b14f479e55ebd550bcc78899
Vendor advisories and official records. Exploit/PoC links are deliberately left out.