Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files

—No exploit Fix available

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.27% (FIRST EPSS).
  • Fixed version: Linux Linux 635bc4def026a24e071436f4f356ea08c0eed6ff, 6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91, 7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 635bc4def026a24e071436f4f356ea08c0eed6ff, 6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91, 7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 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: fsnotify: do not generate ACCESS/MODIFY events on child for special files inotify/fanotify do not allow users with no read access to a file to subscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the same user to subscribe for watching events on children when the user has access to the parent directory (e.g. /dev). Users with no read access to a file but with read access to its parent directory can still stat the file and see if it was accessed/modified via atime/mtime change. The same is not true for special files (e.g. /dev/null). Users will not generally observe atime/mtime changes when other users read/write to special files, only when someone sets atime/mtime via utimensat(). Align fsnotify events with this stat behavior and do not generate ACCESS/MODIFY events to parent watchers on read/write of special files. The events are still generated to parent watchers on utimensat(). This closes some side-channels that could be possibly used for information exfiltration [1]. [1] https://snee.la/pdf/pubs/file-notification-attacks.pdf

Published
Jan 13, 2026
Updated
Nov 10, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

0

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-2025-68788

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

    • 2.6.36affected
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before df2711544b050aba703e6da418c53c7dc5d443caaffected · git
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before 859bdf438f01d9aa7f84b09c1202d548c7cad9e8affected · git
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before 6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91affected · git
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before e0643d46759db8b84c0504a676043e5e341b6c81affected · git
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before 82f7416bcbd951549e758d15fc1a96a5afc2e900affected · git
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before 7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6affected · git
    • 72acc854427948efed7a83da27f7dc3239ac9afc and later · before 635bc4def026a24e071436f4f356ea08c0eed6ffaffected · git
    • before 2.6.36not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1

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-2025-68785Jan 13, 2026 · net: openvswitch: fix middle attribute validation in push_nsh() action
    28Monitor
  • ← EarlierCVE-2025-68787Jan 13, 2026 · netrom: Fix memory leak in nr_sendmsg()
    0Monitor
  • Later →CVE-2025-68793Jan 13, 2026 · drm/amdgpu: fix a job->pasid access race in gpu recovery
    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 Linux635bc4def026a24e071436f4f356ea08c0eed6ffVendor (CNA)
Linux Linux6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91Vendor (CNA)
Linux Linux7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6Vendor (CNA)
Linux Linux82f7416bcbd951549e758d15fc1a96a5afc2e900Vendor (CNA)
Linux Linux859bdf438f01d9aa7f84b09c1202d548c7cad9e8Vendor (CNA)
Linux Linuxdf2711544b050aba703e6da418c53c7dc5d443caVendor (CNA)
Linux Linuxe0643d46759db8b84c0504a676043e5e341b6c81Vendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

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.

Variant candidates

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

  • CVE-2026-72103214 days apartdm: avoid leaking the caller's thread keyring via the table device file
    29Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

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

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

References

All records