CVE-2026-68448ovl: check access to copy_file_range source with src mounter creds
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 13 days later
· 13 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 5dae222a5ff0c269730393018a5539cc970a4726 – < 214c292d135ac11d32c766c6c4276092b80b2fbd
- affected 5dae222a5ff0c269730393018a5539cc970a4726 – < 7e13e5b087375f1aee1e930503d20efa7084c0fa
- affected 5dae222a5ff0c269730393018a5539cc970a4726 – < 46c296aa678828105842eee29a147508d803d926
- affected 5dae222a5ff0c269730393018a5539cc970a4726 – < 9ec22c8113d8cf72ed7197bb61037dcad09e50d8
- affected 5dae222a5ff0c269730393018a5539cc970a4726 – < 1f4a107439d2e43db176e34919933e617cb7f2c5
- affected 5dae222a5ff0c269730393018a5539cc970a4726 – < a1e0eb8f55cfe09bb31a202a388babc411292656
- affected 5.3
- unaffected < 5.3
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/214c292d135ac11d32c766c6c4276092b80b2fbd (opens in a new tab)
- https://git.kernel.org/stable/c/7e13e5b087375f1aee1e930503d20efa7084c0fa (opens in a new tab)
- https://git.kernel.org/stable/c/46c296aa678828105842eee29a147508d803d926 (opens in a new tab)
- https://git.kernel.org/stable/c/9ec22c8113d8cf72ed7197bb61037dcad09e50d8 (opens in a new tab)
- https://git.kernel.org/stable/c/1f4a107439d2e43db176e34919933e617cb7f2c5 (opens in a new tab)
- https://git.kernel.org/stable/c/a1e0eb8f55cfe09bb31a202a388babc411292656 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-57054 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68448)Record last updated .