Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Fixed version: Linux Linux 1f4a107439d2e43db176e34919933e617cb7f2c5, 46c296aa678828105842eee29a147508d803d926, 7e13e5b087375f1aee1e930503d20efa7084c0fa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 1f4a107439d2e43db176e34919933e617cb7f2c5, 46c296aa678828105842eee29a147508d803d926, 7e13e5b087375f1aee1e930503d20efa7084c0fa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 12, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-68448

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.3affected
    • 5dae222a5ff0c269730393018a5539cc970a4726 and later · before 7e13e5b087375f1aee1e930503d20efa7084c0faaffected · git
    • 5dae222a5ff0c269730393018a5539cc970a4726 and later · before 46c296aa678828105842eee29a147508d803d926affected · git
    • 5dae222a5ff0c269730393018a5539cc970a4726 and later · before 9ec22c8113d8cf72ed7197bb61037dcad09e50d8affected · git
    • 5dae222a5ff0c269730393018a5539cc970a4726 and later · before 1f4a107439d2e43db176e34919933e617cb7f2c5affected · git
    • 5dae222a5ff0c269730393018a5539cc970a4726 and later · before a1e0eb8f55cfe09bb31a202a388babc411292656affected · git
    • before 5.3not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver
    • 6.18.42 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.68.1.el10_26.12.0-211.68.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-68446Aug 12, 2026 · drm/vmwgfx: Validate vmw_surface_metadata::array_size
    31Monitor
  • ← EarlierCVE-2026-68447Aug 12, 2026 · drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size
    28Monitor
  • Later →CVE-2026-68451Aug 13, 2026 · s390/zcrypt: Validate length for CCA ECC private key requests
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1f4a107439d2e43db176e34919933e617cb7f2c5Vendor (CNA)
Linux Linux46c296aa678828105842eee29a147508d803d926Vendor (CNA)
Linux Linux7e13e5b087375f1aee1e930503d20efa7084c0faVendor (CNA)
Linux Linux9ec22c8113d8cf72ed7197bb61037dcad09e50d8Vendor (CNA)
Linux Linuxa1e0eb8f55cfe09bb31a202a388babc411292656Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.68.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.60.1.el9_8 · AlmaLinux:9Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records