CVE-2026-43391: nsfs: tighten permission checks for handle opening
In the Linux kernel, the following vulnerability has been resolved:
nsfs: tighten permission checks for handle opening
Even privileged services should not necessarily be able to see other
privileged service's namespaces so they can't leak information to each
other. Use may_see_all_namespaces() helper that centralizes this policy
until the nstree adapts.
Security readout for executives and security teams
Plain-English summary
A Linux kernel permission flaw could let a locally authenticated, low-privilege actor open namespace handles belonging to privileged services that should remain isolated. This may expose sensitive cross-service information and weaken security boundaries. The supplied CVSS score is 8.8, but exploitation requires local access.
Executive priority
Treat this as an accelerated patching priority for shared or isolation-sensitive Linux hosts. The high CVSS score supports urgency, while the local attack requirement and lack of cited active exploitation make it less urgent than an internet-exploitable emergency. Obtain distribution-specific fixed-version guidance before scheduling deployment.
Technical view
The nsfs handle-opening path lacked the centralized may_see_all_namespaces() authorization policy. Consequently, privilege alone could permit visibility into another privileged service’s namespaces. The resolution tightens this check. The supplied CVSS vector reports local, low-complexity exploitation with low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is most relevant on affected Linux systems where untrusted or compromised local users and services can interact with namespace handles. Multi-service, containerized, or shared-host environments may warrant extra attention. The supplied affected-version data names 6.18, 6.18.50, 6.19.9, and 7.0, but does not clearly define complete vulnerable ranges.
Exploitation context
The bundle marks this CVE as absent from KEV, and no supplied source claims active exploitation or provides a public exploit. The attack vector is local, so this is not presented as a direct unauthenticated network compromise. A foothold or low-privilege local access is required according to the CVSS vector.
Researcher notes
The record provides three stable-kernel commits but does not map them to branches or clearly express affected ranges. No CWE, proof of concept, detection signature, or exploitation telemetry is supplied. The description directly supports namespace visibility and information-leak risk; the CVSS high integrity and availability impacts are asserted but not explained in the provided narrative.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced nsfs permission fix.
Confirm distribution advisories before interpreting the incomplete affected-version list.
Restrict local access and minimize privileges granted to exposed or untrusted services.
Prioritize shared, containerized, and multi-service hosts where namespace isolation is security-critical.
Validation and detection
Record each system’s running kernel version and distribution build identifier.
Compare installed builds with the distribution vendor’s affected and fixed package guidance.
Verify the deployed kernel includes the may_see_all_namespaces() authorization change.
Review local users and services capable of interacting with namespace handles.
Regression-test namespace-dependent workloads after updating the kernel.
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-43391 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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.