Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-93794

smb/client: flush dirty data before punching a hole

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:45:30 UTC

Severity

unknown

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

In the Linux kernel, the following vulnerability has been resolved:

Source excerpt · Linux

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

5 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

31742c5a331766bc7df6b0d525df00c6cd20d5a6 → before 0c9fcab9bf1ef3516983f3de05a19c5658c7a01e

git versions

31742c5a331766bc7df6b0d525df00c6cd20d5a6 → before 216e469586057c29409e4ef8311d282388c6e251

git versions

31742c5a331766bc7df6b0d525df00c6cd20d5a6 → before 6c265aca08155e519a8f6f6071c59dff4f535f70

git versions

31742c5a331766bc7df6b0d525df00c6cd20d5a6 → before 39562a56cdb515f6635c3e7bfe6629439b18a169

git versions

31742c5a331766bc7df6b0d525df00c6cd20d5a6 → before d7d2adcd022baade5cab65ca492ce63421ce3a6e

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

7 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

3.17

unaffected

0 → before 3.17

semver versions

6.1.191 → through 6.1.*

semver versions

6.6.158 → through 6.6.*

semver versions

6.12.111 → through 6.12.*

semver versions

6.18.53 → through 6.18.*

semver versions

7.2 → through *

original_commit_for_fix versions

unknown

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

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.

References

5 sources
git.kernel.org/stable/c/0c9fcab9bf1ef3516983f3de05a19c5658c7a01e
Source referenceLinux
git.kernel.org/stable/c/216e469586057c29409e4ef8311d282388c6e251
Source referenceLinux
git.kernel.org/stable/c/6c265aca08155e519a8f6f6071c59dff4f535f70
Source referenceLinux
git.kernel.org/stable/c/39562a56cdb515f6635c3e7bfe6629439b18a169
Source referenceLinux
git.kernel.org/stable/c/d7d2adcd022baade5cab65ca492ce63421ce3a6e
Source referenceLinux

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification · not supplied
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-93794

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 3.17

Before: 6.1.191

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 3.17

Before: 6.6.158

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 3.17

Before: 6.12.111

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 3.17

Before: 6.18.53

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 3.17

Before: 7.2

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "3.17",
            "versionEndExcluding": "6.1.191"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "3.17",
            "versionEndExcluding": "6.6.158"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "3.17",
            "versionEndExcluding": "6.12.111"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "3.17",
            "versionEndExcluding": "6.18.53"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "3.17",
            "versionEndExcluding": "7.2"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-10-30

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.