CVE-2026-43408: ceph: add a bunch of missing ceph_path_info initializers
Noroxi assessment
Priority: Monitor (action score 31/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 43323a5934b660afae687e8e4e95ac328615a5c4, 453df1f4535842bf17ff1885a225e153d7ee3374, 6.12.78.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 43323a5934b660afae687e8e4e95ac328615a5c4, 453df1f4535842bf17ff1885a225e153d7ee3374, 6.12.78 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: ceph: add a bunch of missing ceph_path_info initializers ceph_mdsc_build_path() must be called with a zero-initialized ceph_path_info parameter, or else the following ceph_mdsc_free_path_info() may crash. Example crash (on Linux 6.18.12): virt_to_cache: Object is not a Slab page! WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6732 kmem_cache_free+0x316/0x400 [...] Call Trace: [...] ceph_open+0x13d/0x3e0 do_dentry_open+0x134/0x480 vfs_open+0x2a/0xe0 path_openat+0x9a3/0x1160 [...] cache_from_obj: Wrong slab cache. names_cache but object is from ceph_inode_info WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6746 kmem_cache_free+0x2dd/0x400 [...] kernel BUG at mm/slub.c:634! Oops: invalid opcode: 0000 [#1] SMP NOPTI RIP: 0010:__slab_free+0x1a4/0x350 Some of the ceph_mdsc_build_path() callers had initializers, but others had not, even though they were all added by commit 15f519e9f883 ("ceph: fix race condition validating r_parent before applying state"). The ones without initializer are suspectible to random crashes. (I can imagine it could even be possible to exploit this bug to elevate privileges.) Unfortunately, these Ceph functions are undocumented and its semantics can only be derived from the code. I see that ceph_mdsc_build_path() initializes the structure only on success, but not on error. Calling ceph_mdsc_free_path_info() after a failed ceph_mdsc_build_path() call does not even make sense, but that's what all callers do, and for it to be safe, the structure must be zero-initialized. The least intrusive approach to fix this is therefore to add initializers everywhere.
- Published
- May 8, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-476
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.12.48 and later · before 6.12.78
- linux linux kernel6.16.8 and later · before 6.17
- linux linux kernel6.17.1 and later · before 6.18.19
- linux linux kernel6.19 and later · before 6.19.9
- linux linux kernel6.17
- linux linux kernel7.0
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
- dc5aad078abc416dd3d555c50f5308c16ba918a7, 2bfe45987eb346e299d9f763f9cd05f77011519f, 6.17affected
- db378e6f83ec705c6091c65d482d555edc2b0a72 and later · before 644b47f0574fd82aeb9d00317eca8d1f2a525c8caffected · git
- 15f519e9f883b316d86e2bb6b767a023aafd9d83 and later · before 8be8911f590813e6f90bc6407ced1b23e50bc5daaffected · git
- 15f519e9f883b316d86e2bb6b767a023aafd9d83 and later · before 453df1f4535842bf17ff1885a225e153d7ee3374affected · git
- 15f519e9f883b316d86e2bb6b767a023aafd9d83 and later · before 43323a5934b660afae687e8e4e95ac328615a5c4affected · git
- 6.12.48 and later · before 6.12.78affected · semver
- 6.6.160 and later · before 6.7affected · semver
- 6.16.8 and later · before 6.17affected · semver
- before 6.17not affected · semver
- 6.12.78 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
+53
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43406May 8, 2026 · libceph: prevent potential out-of-bounds reads in process_message_header()36Monitor
- ← EarlierCVE-2026-43407May 8, 2026 · libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply()36Monitor
- Later →CVE-2026-43409May 8, 2026 · kprobes: avoid crash when rmmod/insmod after ftrace killed22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 43323a5934b660afae687e8e4e95ac328615a5c4 | Vendor (CNA) |
| Linux Linux | 453df1f4535842bf17ff1885a225e153d7ee3374 | Vendor (CNA) |
| Linux Linux | 6.12.78 | Vendor (CNA) |
| Linux Linux | 6.17 | Vendor (CNA) |
| Linux Linux | 6.7 | Vendor (CNA) |
| Linux Linux | 644b47f0574fd82aeb9d00317eca8d1f2a525c8c | Vendor (CNA) |
| Linux Linux | 8be8911f590813e6f90bc6407ced1b23e50bc5da | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.85-1 · Debian:13 | Package 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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0213 · May 12, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.