Skip to content
Heist/ feed
Back to feed
UnratedFix available

smb/client: flush dirty data before punching a hole

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: smb/client: flush dirty data before punching a hole Punching a hole after a large buffered write may leave the range reported as data. Reproduce it with: xfs_io -f \ -c "pwrite -b 3m -S 0x61 0 3m" \ -c "fpunch 1m 1m" \ -c "seek -h 0" \ -c "seek -d 1m" \ /mnt/test/repro Punching 1 MiB at offset 1 MiB should produce: 0 1 MiB 2 MiB 3 MiB | DATA | HOLE | DATA | EOF Instead, the entire file is reported as data. SEEK_HOLE(0) returns EOF, and SEEK_DATA(1M) returns 1M. This happens because a dirty folio spanning the punched range can be written back after the punch and refill the hole. Fix this by flushing and waiting for dirty data in the punched range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA. The xfstests generic/539 pass against Samba/ksmbd with this change.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.1.191, 6.12.111, 6.18.53, 6.6.158
CVEs
CVE-2026-93794
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 20:34 UTC · Revision 1

Source evidence

smb/client: flush dirty data before punching a hole

core-osv · Original source

Published 24 Sept 2026, 16:02 UTC

In the Linux kernel, the following vulnerability has been resolved: smb/client: flush dirty data before punching a hole Punching a hole after a large buffered write may leave the range reported as data. Reproduce it with: xfs_io -f \ -c "pwrite -b 3m -S 0x61 0 3m" \ -c "fpunch 1m 1m" \ -c "seek -h 0" \ -c "seek -d 1m" \ /mnt/test/repro Punching 1 MiB at offset 1 MiB should produce: 0 1 MiB 2 MiB 3 MiB | DATA | HOLE | DATA | EOF Instead, the entire file is reported as data. SEEK_HOLE(0) returns EOF, and SEEK_DATA(1M) returns 1M. This happens because a dirty folio spanning the punched range can be written back after the punch and refill the hole. Fix this by flushing and waiting for dirty data in the punched range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA. The xfstests generic/539 pass against Samba/ksmbd with this change.

osv:CVE-2026-93794

Kernel

Fixed versions: 6.1.191, 6.6.158, 6.12.111, 6.18.53

Complete source record
{
  "id": "4de88bfb51414c00debd526b153e4cb0f0f466598929948947acbf4c34f327c0",
  "url": "https://osv.dev/vulnerability/CVE-2026-93794",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "smb/client: flush dirty data before punching a hole",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: smb/client: flush dirty data before punching a hole Punching a hole after a large buffered write may leave the range reported as data. Reproduce it with: xfs_io -f \\ -c \"pwrite -b 3m -S 0x61 0 3m\" \\ -c \"fpunch 1m 1m\" \\ -c \"seek -h 0\" \\ -c \"seek -d 1m\" \\ /mnt/test/repro Punching 1 MiB at offset 1 MiB should produce: 0 1 MiB 2 MiB 3 MiB | DATA | HOLE | DATA | EOF Instead, the entire file is reported as data. SEEK_HOLE(0) returns EOF, and SEEK_DATA(1M) returns 1M. This happens because a dirty folio spanning the punched range can be written back after the punch and refill the hole. Fix this by flushing and waiting for dirty data in the punched range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA. The xfstests generic/539 pass against Samba/ksmbd with this change.",
    "evidence": "osv:CVE-2026-93794",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.191",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.158",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.111",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.53",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-93794",
      "aliases": [
        "CVE-2026-93794"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "31742c5a331766bc7df6b0d525df00c6cd20d5a6"
                },
                {
                  "fixed": "0c9fcab9bf1ef3516983f3de05a19c5658c7a01e"
                },
                {
                  "fixed": "216e469586057c29409e4ef8311d282388c6e251"
                },
                {
                  "fixed": "6c265aca08155e519a8f6f6071c59dff4f535f70"
                },
                {
                  "fixed": "39562a56cdb515f6635c3e7bfe6629439b18a169"
                },
                {
                  "fixed": "d7d2adcd022baade5cab65ca492ce63421ce3a6e"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93794.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "3.17.0"
                },
                {
                  "fixed": "6.1.191"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.158"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.111"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.53"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93794.json"
          }
        }
      ],
      "modified": "2026-11-01T02:30:55.408613300Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/0c9fcab9bf1ef3516983f3de05a19c5658c7a01e",
        "https://git.kernel.org/stable/c/216e469586057c29409e4ef8311d282388c6e251",
        "https://git.kernel.org/stable/c/39562a56cdb515f6635c3e7bfe6629439b18a169",
        "https://git.kernel.org/stable/c/6c265aca08155e519a8f6f6071c59dff4f535f70",
        "https://git.kernel.org/stable/c/d7d2adcd022baade5cab65ca492ce63421ce3a6e",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93794.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-93794",
        "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/93xxx/CVE-2026-93794.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-93794",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 506729,
  "published_at": "2026-09-24T16:02:27.716+00:00"
}