CVE-2025-68788

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.12.64, <df2711544b050aba703e6da418c53c7dc5d443ca, <=6.1.*, <e0643d46759db8b84c0504a676043e5e341b6c81, <859bdf438f01d9aa7f84b09c1202d548c7cad9e8, <=6.12.*, 6.1.160, 0, 2.6.36, 6.6.120, 5.15.198, <7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6, <=5.10.*, <=6.6.*, 6.18.3, 72acc854427948efed7a83da27f7dc3239ac9afc, <=6.18.*, <2.6.36, 5.10.248, <82f7416bcbd951549e758d15fc1a96a5afc2e900, <=*, <=5.15.*, 6.19, <6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91, <635bc4def026a24e071436f4f356ea08c0eed6ff

Description

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

Gravité et risque d'exploitation

CVE-2025-68788 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.24 %, ce qui la place devant 14.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12.64, <df2711544b050aba703e6da418c53c7dc5d443ca, <=6.1.*, <e0643d46759db8b84c0504a676043e5e341b6c81, <859bdf438f01d9aa7f84b09c1202d548c7cad9e8, <=6.12.*, 6.1.160, 0, 2.6.36, 6.6.120, 5.15.198, <7a93edb23bcf07a3aaf8b598edfc2faa8fbcc0b6, <=5.10.*, <=6.6.*, 6.18.3, 72acc854427948efed7a83da27f7dc3239ac9afc, <=6.18.*, <2.6.36, 5.10.248, <82f7416bcbd951549e758d15fc1a96a5afc2e900, <=*, <=5.15.*, 6.19, <6a7d7d96eeeab7af2bd01afbb3d9878a11a13d91, <635bc4def026a24e071436f4f356ea08c0eed6ff) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références