dbcve.org
Linux KernelOperating system · Linux

CVE-2018-14614

MEDIUM · 5.5 CVSS v3.0 Published 2018-07-27
Fix available
A fix is available. Upgrade to after 4.17.10 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in the Linux kernel through 4.17.10. There is an out-of-bounds access in __remove_dirty_segment() in fs/f2fs/segment.c when mounting an f2fs image.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A out-of-bounds access vulnerability exists in the Linux kernel's f2fs (Flash-Friendly File System) implementation. Specifically, the __remove_dirty_segment() function in fs/f2fs/segment.c lacks proper bounds checking when processing f2fs images, allowing memory access beyond allocated buffers during mount operations.

MitigationApply the upstream kernel patch addressing the bounds check in __remove_dirty_segment() or update to a Linux kernel version newer than 4.17.10 that includes the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:<= 4.17.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run 'uname -r' to retrieve the running kernel version and compare it to the affected range (versions <= 4.17.10)
    Affected if The installed kernel version is 4.17.10 or earlier
  2. Identify f2fs filesystem usage
    Run 'mount | grep f2fs' or check /proc/filesystems for f2fs support to see if f2fs is currently mounted or available
    Affected if Any f2fs filesystem is mounted on the system
  3. Verify f2fs module is loaded
    Run 'lsmod | grep f2fs' to check if the f2fs kernel module is loaded, or check /sys/fs/f2fs/ for mounted f2fs instances
    Affected if The f2fs module is loaded or f2fs filesystems exist in /sys/fs/f2fs/

The system is affected if the kernel version is 4.17.10 or earlier AND f2fs is in use (either a module is loaded or a f2fs filesystem is mounted).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 4.17.10
Interim mitigation

Apply the upstream kernel patch addressing the bounds check in __remove_dirty_segment() or update to a Linux kernel version newer than 4.17.10 that includes the fix.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14614 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data