CVE-2026-68448None▾ SunlitIn 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 …
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= 5dae222a5ff0c269730393018a5539cc970a4726 < 7e13e5b087375f1aee1e930503d20efa7084c0faLinux >= 5dae222a5ff0c269730393018a5539cc970a4726 < 46c296aa678828105842eee29a147508d803d926Linux >= 5dae222a5ff0c269730393018a5539cc970a4726 < 9ec22c8113d8cf72ed7197bb61037dcad09e50d8Linux >= 5dae222a5ff0c269730393018a5539cc970a4726 < 1f4a107439d2e43db176e34919933e617cb7f2c5Linux >= 5dae222a5ff0c269730393018a5539cc970a4726 < a1e0eb8f55cfe09bb31a202a388babc411292656Linux 5.3Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-98869Nonebpf: Infer zext_dst based on static register liveness analysis
CVE-2023-7356NoneBluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID
CVE-2026-98766Noneusb: gadget: aspeed-vhub: cancel wake work on device removal
CVE-2026-98768Medium· 4.7usb: typec: anx7411 - stop the IRQ before destroying the workqueue
CVE-2026-98767Noneusb: dwc3: gadget: fix IRQ storm on invalid event buffer count
CVE-2026-98770Noneusb: gadget: midi2: Fix the jack descriptor array sizes