CVE-2025-68315: f2fs: fix to detect potential corrupted nid in free_nid_list
Noroxi assessment
Priority: Monitor (action score 39/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.43% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 6b9525596a83cd5b7bbc2c7bd5f9ad9cf5ad60fa, 88b2ddb0c4f1dc874d4598e78cc830c64315ed86, 8fc6056dcf79937c46c97fa4996cda65956437a9.
Low priority for now. Upgrade to Linux Linux 6b9525596a83cd5b7bbc2c7bd5f9ad9cf5ad60fa, 88b2ddb0c4f1dc874d4598e78cc830c64315ed86, 8fc6056dcf79937c46c97fa4996cda65956437a9 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 detect potential corrupted nid in free_nid_list As reported, on-disk footer.ino and footer.nid is the same and out-of-range, let's add sanity check on f2fs_alloc_nid() to detect any potential corruption in free_nid_list.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- —
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.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.
Is your version affected? Check itNoroxi 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.8affected
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 88b2ddb0c4f1dc874d4598e78cc830c64315ed86affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 9337ed5e777e1c19854928cba7a8131dd00e611baffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 6b9525596a83cd5b7bbc2c7bd5f9ad9cf5ad60faaffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before adbcb34f03abb89e681a5907c4c3ce4bf224991daffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 8fc6056dcf79937c46c97fa4996cda65956437a9affected · git
- before 3.8not affected · semver
- 6.1.175 and later · up to and including 6.1.*not affected · semver
- 6.6.140 and later · up to and including 6.6.*not affected · semver
- 6.12.58 and later · up to and including 6.12.*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.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-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-2025-68313Dec 16, 2025 · x86/CPU/AMD: Add RDSEED fix for Zen528Monitor
- ← EarlierCVE-2025-68314Dec 16, 2025 · drm/msm: make sure last_fence is always updated35Monitor
- Later →CVE-2025-68316Dec 16, 2025 · scsi: ufs: core: Fix invalid probe error return value0Monitor
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 | 6b9525596a83cd5b7bbc2c7bd5f9ad9cf5ad60fa | Vendor (CNA) |
| Linux Linux | 88b2ddb0c4f1dc874d4598e78cc830c64315ed86 | Vendor (CNA) |
| Linux Linux | 8fc6056dcf79937c46c97fa4996cda65956437a9 | Vendor (CNA) |
| Linux Linux | 9337ed5e777e1c19854928cba7a8131dd00e611b | Vendor (CNA) |
| Linux Linux | adbcb34f03abb89e681a5907c4c3ce4bf224991d | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.