CVE-2026-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match()
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 ]
Security readout for executives and security teams
Plain-English summary
CVE-2026-23189 is a Linux kernel CephFS client bug that can trigger a NULL pointer dereference during metadata-server authorization matching. Business risk is mainly availability for systems that mount CephFS with affected kernels. The source bundle does not provide CVSS, confirmed exploitation, or distribution-specific fixes.
Executive priority
Treat as a targeted availability risk for CephFS-backed Linux infrastructure. Prioritize patching where CephFS supports production workloads, shared storage, or critical services. Broader enterprise urgency is unclear without CVSS, exploitation evidence, or distribution impact statements.
Technical view
The issue is in ceph_mds_auth_match() when fs_name is NULL. The fix changes CephFS MDSMap decoding to store an extracted filesystem name in struct ceph_mdsmap, defaulting old CephFS filesystems to "cephfs", so authorization checks compare against a real filesystem name.
Likely exposure
Exposure appears limited to Linux systems using the kernel CephFS client on affected kernel builds listed in the CVE data, including 6.18, 6.18.10, 6.19, and 6.12.70. Systems not mounting CephFS are not shown as exposed by the provided sources.
Exploitation context
The source bundle does not report active exploitation, public exploit availability, or CISA KEV listing. The described failure condition is a kernel NULL pointer dereference tied to CephFS client metadata authorization handling, suggesting availability impact, but the sources do not quantify severity.
Researcher notes
The CVE text identifies a regression starting from 6.18-rc1, but the affected-version data also lists 6.12.70. Validate exact backport lineage before scoping. The provided fixes focus on decoding and comparing the filesystem name from MDSMap for stricter authorization behavior.
Mitigation direction
Apply Linux kernel stable fixes referenced by the CVE record.
Use distribution vendor advisories for packaged kernel update guidance.
Prioritize systems that mount CephFS through the kernel client.
Restrict CephFS usage on affected kernels until patched where feasible.
Check vendor guidance if running custom or backported kernels.
Validation and detection
Inventory Linux kernel versions on CephFS client hosts.
Confirm whether hosts mount CephFS using the kernel client.
Compare deployed kernels against affected and fixed versions in advisories.
Verify the relevant stable commit is present in custom kernels.
Monitor kernel logs for CephFS-related crashes or NULL dereferences.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23189 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 16:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.