CVE-2026-89838 (GCVE-0-2026-89838)
Vulnerability from cvelistv5
Published
2026-09-16 10:31
Modified
2026-10-21 12:49
Severity ?
7.1 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Summary
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.
References
Impacted products
Vendor Product Version
Linux Linux Version: f356fe0cba0e3523e538987916bd2acedd4e6f41
Version: f356fe0cba0e3523e538987916bd2acedd4e6f41
Version: f356fe0cba0e3523e538987916bd2acedd4e6f41
Version: f356fe0cba0e3523e538987916bd2acedd4e6f41
Version: f356fe0cba0e3523e538987916bd2acedd4e6f41
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/recovery.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "e754120f8ede55cc773ade108cf7e5b17c859c46",
              "status": "affected",
              "version": "f356fe0cba0e3523e538987916bd2acedd4e6f41",
              "versionType": "git"
            },
            {
              "lessThan": "7ab1780074943508534343e1e5e5ab0c9ef9dd7b",
              "status": "affected",
              "version": "f356fe0cba0e3523e538987916bd2acedd4e6f41",
              "versionType": "git"
            },
            {
              "lessThan": "35c5abccd0924b02ad34126f562d93c8d75b0831",
              "status": "affected",
              "version": "f356fe0cba0e3523e538987916bd2acedd4e6f41",
              "versionType": "git"
            },
            {
              "lessThan": "317d32e1a8deaf1c01c388badc667334c39e62ca",
              "status": "affected",
              "version": "f356fe0cba0e3523e538987916bd2acedd4e6f41",
              "versionType": "git"
            },
            {
              "lessThan": "01027b2fcb74dade59fb833b51023f6593b6a9a2",
              "status": "affected",
              "version": "f356fe0cba0e3523e538987916bd2acedd4e6f41",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/recovery.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.11"
            },
            {
              "lessThan": "3.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.160",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.112",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.53",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.160",
                  "versionStartIncluding": "3.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.112",
                  "versionStartIncluding": "3.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.53",
                  "versionStartIncluding": "3.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "3.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "3.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: limit recovery filename logging to stored length\n\nF2FS stores recovery filenames as a length plus a fixed-size i_name\nbuffer.  The buffer is not NUL-terminated, but recover_inode() and\nrecover_dentry() print it with %s.\n\nFor a 255-byte filename, recovery logging can read past i_name into the\nfollowing raw inode fields.\n\nPrint the name with a precision bounded by i_namelen and F2FS_NAME_LEN."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - recover_inode() and recover_dentry() run only during local f2fs roll-forward in f2fs_fill_super() -\u003e f2fs_recover_fsync_data(). This is a local block filesystem (Android userdata/portable storage), not a network protocol path such as ksmbd or nfsd.\nAC:L - A crafted f2fs image with a 255-byte non-NUL i_name and a pending fsync node makes printk %s over-read deterministically on mount. Roll-forward is default-enabled; no race or attacker-uncontrollable layout is required.\nPR:L - f2fs lacks FS_USERNS_MOUNT, but Android vold auto-mounts f2fs portable/adoptable storage and desktop/kiosk udisks2/polkit mounts removable media for an ordinary console user, so init-namespace root is not required.\nUI:N - The attacker supplies the crafted image; vold/udisks auto-mount runs roll-forward recovery without a separate deliberate victim mount or open. Recovery also fires automatically on the next mount after an unclean shutdown.\nS:U - The over-read and any resulting oops stay in the host kernel address space and security authority. This is not a VM escape, IOMMU bypass, or sandbox boundary crossing.\nC:H - recover_inode()/recover_dentry() pass the 255-byte, non-NUL-terminated i_name to printk %s with no precision, so vsprintf scans past the field and the rest of the 4KB node folio into adjacent kernel memory and copies it into dmesg, an unbounded OOB read.\nI:N - The defect is a read-only printk over-read of i_name; it does not write kernel memory, corrupt adjacent objects, or provide a control-flow hijack primitive.\nA:H - Unbounded %s scanning off the node folio can walk into unmapped pages or trip KASAN/page-poisoning and oops/panic the kernel during mount recovery, fully denying availability."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-21T12:49:01.146Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/e754120f8ede55cc773ade108cf7e5b17c859c46"
        },
        {
          "url": "https://git.kernel.org/stable/c/7ab1780074943508534343e1e5e5ab0c9ef9dd7b"
        },
        {
          "url": "https://git.kernel.org/stable/c/35c5abccd0924b02ad34126f562d93c8d75b0831"
        },
        {
          "url": "https://git.kernel.org/stable/c/317d32e1a8deaf1c01c388badc667334c39e62ca"
        },
        {
          "url": "https://git.kernel.org/stable/c/01027b2fcb74dade59fb833b51023f6593b6a9a2"
        }
      ],
      "title": "f2fs: limit recovery filename logging to stored length",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89838",
    "datePublished": "2026-09-16T10:31:12.746Z",
    "dateReserved": "2026-09-11T19:38:34.769Z",
    "dateUpdated": "2026-10-21T12:49:01.146Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.