Skip to content
Heist/ feed
Back to feed
HighFix available

fs/ntfs3: validate rec->used in journal-replay file record check

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate rec->used in journal-replay file record check check_file_record() validates rec->total against the record size but never validates rec->used. The do_action() journal-replay handlers read rec->used from disk and use it to compute memmove lengths: DeleteAttribute: memmove(attr, ..., used - asize - roff) CreateAttribute: memmove(..., attr, used - roff) change_attr_size: memmove(..., used - PtrOffset(rec, next)) When rec->used is smaller than the offset of a validated attribute, or larger than the record size, these subtractions can underflow allowing us to copy huge amounts of memory in to a 4kb buffer, generally considered a bad idea overall. This requires a corrupted filesystem, which isn't a threat model the kernel really needs to worry about, but checking for such an obvious out-of-bounds value is good to keep things robust, especially on journal replay Fix this up by bounding rec->used correctly. This is much like commit b2bc7c44ed17 ("fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot") which checked different values in this same switch statement.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.15.209, 6.1.175, 6.12.84, 6.18.25, 6.6.136, 7.0.2
CVEs
CVE-2026-31716
Confirmed fixed CVEs
Not specified
Updated in this feed
6 Nov 2026, 01:57 UTC · Revision 1

Source evidence

fs/ntfs3: validate rec->used in journal-replay file record check

core-osv · Original source

Published 1 May 2026, 13:56 UTC

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate rec->used in journal-replay file record check check_file_record() validates rec->total against the record size but never validates rec->used. The do_action() journal-replay handlers read rec->used from disk and use it to compute memmove lengths: DeleteAttribute: memmove(attr, ..., used - asize - roff) CreateAttribute: memmove(..., attr, used - roff) change_attr_size: memmove(..., used - PtrOffset(rec, next)) When rec->used is smaller than the offset of a validated attribute, or larger than the record size, these subtractions can underflow allowing us to copy huge amounts of memory in to a 4kb buffer, generally considered a bad idea overall. This requires a corrupted filesystem, which isn't a threat model the kernel really needs to worry about, but checking for such an obvious out-of-bounds value is good to keep things robust, especially on journal replay Fix this up by bounding rec->used correctly. This is much like commit b2bc7c44ed17 ("fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot") which checked different values in this same switch statement.

osv:CVE-2026-31716

Kernel

Fixed versions: 5.15.209, 6.1.175, 6.6.136, 6.12.84, 6.18.25, 7.0.2

Complete source record
{
  "id": "661c6a7d19f2a65db961c25430105dd7abad0ebba195f409ef7301752fd0e51d",
  "url": "https://osv.dev/vulnerability/CVE-2026-31716",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "fs/ntfs3: validate rec->used in journal-replay file record check",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate rec->used in journal-replay file record check check_file_record() validates rec->total against the record size but never validates rec->used. The do_action() journal-replay handlers read rec->used from disk and use it to compute memmove lengths: DeleteAttribute: memmove(attr, ..., used - asize - roff) CreateAttribute: memmove(..., attr, used - roff) change_attr_size: memmove(..., used - PtrOffset(rec, next)) When rec->used is smaller than the offset of a validated attribute, or larger than the record size, these subtractions can underflow allowing us to copy huge amounts of memory in to a 4kb buffer, generally considered a bad idea overall. This requires a corrupted filesystem, which isn't a threat model the kernel really needs to worry about, but checking for such an obvious out-of-bounds value is good to keep things robust, especially on journal replay Fix this up by bounding rec->used correctly. This is much like commit b2bc7c44ed17 (\"fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot\") which checked different values in this same switch statement.",
    "evidence": "osv:CVE-2026-31716",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.15.209",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.175",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.136",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.84",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.25",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.0.2",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-31716",
      "aliases": [
        "CVE-2026-31716"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "b46acd6a6a627d876898e1c84d3f84902264b445"
                },
                {
                  "fixed": "8e64d33198b5a0fb14a452708bad844f94f03b2c"
                },
                {
                  "fixed": "1393a467a9607e62123806de7d4c3a3e54e396a9"
                },
                {
                  "fixed": "f90b8a1798b750755a9e9aee66678f0a1820bbaf"
                },
                {
                  "fixed": "4b1613d7e2deda831a97e427d1ea586e50fe1be5"
                },
                {
                  "fixed": "0112e6279420d4005b3d57af36fb45c01b8d0116"
                },
                {
                  "fixed": "f79d0403ea20a81bc29105bba54fbcab54e8c403"
                },
                {
                  "fixed": "0ca0485e4b2e837ebb6cbd4f2451aba665a03e4b"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31716.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.15.0"
                },
                {
                  "fixed": "5.15.209"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.175"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.136"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.84"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.25"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.0.2"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31716.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:46.166216974Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/0112e6279420d4005b3d57af36fb45c01b8d0116",
        "https://git.kernel.org/stable/c/0ca0485e4b2e837ebb6cbd4f2451aba665a03e4b",
        "https://git.kernel.org/stable/c/1393a467a9607e62123806de7d4c3a3e54e396a9",
        "https://git.kernel.org/stable/c/4b1613d7e2deda831a97e427d1ea586e50fe1be5",
        "https://git.kernel.org/stable/c/8e64d33198b5a0fb14a452708bad844f94f03b2c",
        "https://git.kernel.org/stable/c/f79d0403ea20a81bc29105bba54fbcab54e8c403",
        "https://git.kernel.org/stable/c/f90b8a1798b750755a9e9aee66678f0a1820bbaf",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31716.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-31716",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31716.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-31716",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 514064,
  "published_at": "2026-05-01T13:56:11.263+00:00"
}