Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-89838: f2fs: limit recovery filename logging to stored length

Noroxi assessment

Priority: Monitor (action score 28/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.16% (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 01027b2fcb74dade59fb833b51023f6593b6a9a2, 317d32e1a8deaf1c01c388badc667334c39e62ca, 35c5abccd0924b02ad34126f562d93c8d75b0831.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 01027b2fcb74dade59fb833b51023f6593b6a9a2, 317d32e1a8deaf1c01c388badc667334c39e62ca, 35c5abccd0924b02ad34126f562d93c8d75b0831 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: limit recovery filename logging to stored length F2FS stores recovery filenames as a length plus a fixed-size i_name buffer. The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s. For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields. Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Sep 16, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.1
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.

Follow CVE-2026-89838

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before b8ac8b14b9d92dd2e1cb05fa8994f41f701fbf28affected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before 450ab2e5dbe0ef6e3ed73214256565f6f003d62aaffected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before 3d02c7c8446f5d6793ac67f93bf3f84bf24e3f25affected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before e754120f8ede55cc773ade108cf7e5b17c859c46affected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before 7ab1780074943508534343e1e5e5ab0c9ef9dd7baffected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before 35c5abccd0924b02ad34126f562d93c8d75b0831affected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before 317d32e1a8deaf1c01c388badc667334c39e62caaffected · git
    • f356fe0cba0e3523e538987916bd2acedd4e6f41 and later · before 01027b2fcb74dade59fb833b51023f6593b6a9a2affected · git
    • before 3.11not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89836Sep 16, 2026 · f2fs: fix folio_nr_pages() race after put in large folio invalidate
    31Monitor
  • ← EarlierCVE-2026-89837Sep 16, 2026 · f2fs: fix dentry folio leak in find_in_level
    0Monitor
  • Later →CVE-2026-89839Sep 16, 2026 · f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()
    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 / packageFixed versionSource
Linux Linux01027b2fcb74dade59fb833b51023f6593b6a9a2Vendor (CNA)
Linux Linux317d32e1a8deaf1c01c388badc667334c39e62caVendor (CNA)
Linux Linux35c5abccd0924b02ad34126f562d93c8d75b0831Vendor (CNA)
Linux Linux3d02c7c8446f5d6793ac67f93bf3f84bf24e3f25Vendor (CNA)
Linux Linux450ab2e5dbe0ef6e3ed73214256565f6f003d62aVendor (CNA)
Linux Linux7ab1780074943508534343e1e5e5ab0c9ef9dd7bVendor (CNA)
Linux Linuxb8ac8b14b9d92dd2e1cb05fa8994f41f701fbf28Vendor (CNA)
Linux Linuxe754120f8ede55cc773ade108cf7e5b17c859c46Vendor (CNA)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.6-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data can be read
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
High
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:H/I:N/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

All records