CVE-2024-53221: f2fs: fix null-ptr-deref in f2fs_submit_page_bio()
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.22% (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 32f5e291b7677495f98246eec573767430321c08, 4289be8465924748daa9bf14866eb7f0987d4e39, 8dddc12d03248755d9f709bc1eb9e3ea2bf1b322.
Low priority for now. Upgrade to Linux Linux 32f5e291b7677495f98246eec573767430321c08, 4289be8465924748daa9bf14866eb7f0987d4e39, 8dddc12d03248755d9f709bc1eb9e3ea2bf1b322 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 null-ptr-deref in f2fs_submit_page_bio() There's issue as follows when concurrently installing the f2fs.ko module and mounting the f2fs file system: KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027] RIP: 0010:__bio_alloc+0x2fb/0x6c0 [f2fs] Call Trace: <TASK> f2fs_submit_page_bio+0x126/0x8b0 [f2fs] __get_meta_page+0x1d4/0x920 [f2fs] get_checkpoint_version.constprop.0+0x2b/0x3c0 [f2fs] validate_checkpoint+0xac/0x290 [f2fs] f2fs_get_valid_checkpoint+0x207/0x950 [f2fs] f2fs_fill_super+0x1007/0x39b0 [f2fs] mount_bdev+0x183/0x250 legacy_get_tree+0xf4/0x1e0 vfs_get_tree+0x88/0x340 do_new_mount+0x283/0x5e0 path_mount+0x2b2/0x15b0 __x64_sys_mount+0x1fe/0x270 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e Above issue happens as the biset of the f2fs file system is not initialized before register "f2fs_fs_type". To address above issue just register "f2fs_fs_type" at the last in init_f2fs_fs(). Ensure that all f2fs file system resources are initialized.
- Published
- Dec 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-476
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%
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 kernel5.6 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
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
- 5.6affected
- f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and later · before 4289be8465924748daa9bf14866eb7f0987d4e39affected · git
- f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and later · before bd9197b72d772be7bccc3b66c83a3157cfe2f96faffected · git
- f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and later · before 8dddc12d03248755d9f709bc1eb9e3ea2bf1b322affected · git
- f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and later · before 32f5e291b7677495f98246eec573767430321c08affected · git
- f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and later · before 9e11b1d5fda972f6be60ab732976a7c8e064cd56affected · git
- f543805fcd60f3f9a491cfa2f2dc9284d2569c28 and later · before b7d0a97b28083084ebdd8e5c6bccd12e6ec18faaaffected · git
- before 5.6not affected · semver
- 5.15.209 and later · up to and including 5.15.*not affected · semver
- 6.1.175 and later · up to and including 6.1.*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.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-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-2024-53218Dec 27, 2024 · f2fs: fix race in concurrent f2fs_stop_gc_thread31Monitor
- ← EarlierCVE-2024-53220Dec 27, 2024 · f2fs: fix to account dirty data in __get_secs_required()22Monitor
- Later →CVE-2024-53222Dec 27, 2024 · zram: fix NULL pointer in comp_algorithm_show()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 | 32f5e291b7677495f98246eec573767430321c08 | Vendor (CNA) |
| Linux Linux | 4289be8465924748daa9bf14866eb7f0987d4e39 | Vendor (CNA) |
| Linux Linux | 8dddc12d03248755d9f709bc1eb9e3ea2bf1b322 | Vendor (CNA) |
| Linux Linux | 9e11b1d5fda972f6be60ab732976a7c8e064cd56 | Vendor (CNA) |
| Linux Linux | b7d0a97b28083084ebdd8e5c6bccd12e6ec18faa | Vendor (CNA) |
| Linux Linux | bd9197b72d772be7bccc3b66c83a3157cfe2f96f | Vendor (CNA) |
| debian:linux | 6.1.176-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)
CWE-476 · NULL Pointer DereferenceCVSS 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/4289be8465924748daa9bf14866eb7f0987d4e39
- git.kernel.org/stable/c/8dddc12d03248755d9f709bc1eb9e3ea2bf1b322
- git.kernel.org/stable/c/9e11b1d5fda972f6be60ab732976a7c8e064cd56
- git.kernel.org/stable/c/b7d0a97b28083084ebdd8e5c6bccd12e6ec18faa
- git.kernel.org/stable/c/bd9197b72d772be7bccc3b66c83a3157cfe2f96f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.