Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89838, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Received3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < b8ac8b14b9d92dd2e1cb05fa8994f41f701fbf28
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < 450ab2e5dbe0ef6e3ed73214256565f6f003d62a
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < 3d02c7c8446f5d6793ac67f93bf3f84bf24e3f25
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < e754120f8ede55cc773ade108cf7e5b17c859c46
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < 7ab1780074943508534343e1e5e5ab0c9ef9dd7b
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < 35c5abccd0924b02ad34126f562d93c8d75b0831
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < 317d32e1a8deaf1c01c388badc667334c39e62ca
    • affected f356fe0cba0e3523e538987916bd2acedd4e6f41 – < 01027b2fcb74dade59fb833b51023f6593b6a9a2
  • Linux · Linux

    • affected 3.11
    • unaffected < 3.11
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89838 badge
[![CVE-2026-89838](https://cveledger.app/badge/CVE-2026-89838.svg)](https://cveledger.app/cve/CVE-2026-89838)

Record last updated .