CVE-2026-23189

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : 6.18.10, <=*, <c6f8326f26bd20d648d9a55afd68148d1b6afe28, <=6.12.*, 22c73d52a6d05c5a2053385c0d6cd9984732799d, 6.18, <6.12.70, 6.17.8, <=6.18.*, <57b36ffc8881dd455d875f85c105901974af2130, 6.19, ca3da8b27ab9a0923ad477447cfb8fc7f4b4c523, 0, 6.12.70, 6.12.58, <6.18, <7987cce375ac8ce98e170a77aa2399f2cf6eb99f, 07640d34a781bb2e39020a39137073c03c4aa932

Description

In the Linux kernel, the following vulnerability has been resolved: ceph: fix NULL pointer dereference in ceph_mds_auth_match() The CephFS kernel client has regression starting from 6.18-rc1. We have issue in ceph_mds_auth_match() if fs_name == NULL: const char fs_name = mdsc->fsc->mount_options->mds_namespace; ... if (auth->match.fs_name && strcmp(auth->match.fs_name, fs_name)) { / fsname mismatch, try next one */ return 0; } Patrick Donnelly suggested that: In summary, we should definitely start decoding `fs_name` from the MDSMap and do strict authorizations checks against it. Note that the `-o mds_namespace=foo` should only be used for selecting the file system to mount and nothing else. It's possible no mds_namespace is specified but the kernel will mount the only file system that exists which may have name "foo". This patch reworks ceph_mdsmap_decode() and namespace_equals() with the goal of supporting the suggested concept. Now struct ceph_mdsmap contains m_fs_name field that receives copy of extracted FS name by ceph_extract_encoded_string(). For the case of "old" CephFS file systems, it is used "cephfs" name. [ idryomov: replace redundant %*pE with %s in ceph_mdsmap_decode(), get rid of a series of strlen() calls in ceph_namespace_match(), drop changes to namespace_equals() body to avoid treating empty mds_namespace as equal, drop changes to ceph_mdsc_handle_fsmap() as namespace_equals() isn't an equivalent substitution there ]

Gravité et risque d'exploitation

CVE-2026-23189 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.13 %, ce qui la place devant 2.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.18.10, <=*, <c6f8326f26bd20d648d9a55afd68148d1b6afe28, <=6.12.*, 22c73d52a6d05c5a2053385c0d6cd9984732799d, 6.18, <6.12.70, 6.17.8, <=6.18.*, <57b36ffc8881dd455d875f85c105901974af2130, 6.19, ca3da8b27ab9a0923ad477447cfb8fc7f4b4c523, 0, 6.12.70, 6.12.58, <6.18, <7987cce375ac8ce98e170a77aa2399f2cf6eb99f, 07640d34a781bb2e39020a39137073c03c4aa932) 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