In the Linux kernel, the following vulnerability has been resolved:
smb: client: reject userspace cifs.spnego descriptions
cifs.spnego key descriptions contain authority-bearing fields such as
pid, uid, creduid, and upcall_target that cifs.upcall treats as
kernel-originating inputs. However, userspace can also create keys of
this type through request_key(2) or add_key(2), allowing those fields to
be supplied without CIFS origin.
Only accept cifs.spnego descriptions while CIFS is using its private
spnego_cred to request the key.
Security readout for executives and security teams
Plain-English summary
CVE-2026-46243 is a local Linux kernel SMB/CIFS client flaw. A logged-in local user may be able to supply forged cifs.spnego key data that the CIFS upcall path treats as kernel-originated. The published impact is high for confidentiality, integrity, and availability.
Executive priority
Treat as a high-priority kernel update for Linux systems with local users or CIFS client usage. It is not shown as remotely exploitable or KEV-listed, but local privilege context and high impact justify prompt remediation.
Technical view
The issue is improper validation of userspace-created cifs.spnego key descriptions. Fields such as pid, uid, creduid, and upcall_target are authority-bearing, but request_key(2) or add_key(2) could create matching key types outside CIFS origin. The kernel fix accepts these descriptions only when CIFS uses its private spnego_cred.
Likely exposure
Exposure is most relevant on Linux systems running affected kernels where the SMB/CIFS client and cifs.upcall/SPNEGO authentication path are available. The CVSS vector is local, low complexity, low privilege, no user interaction.
Exploitation context
The bundle marks KEV as false, so active exploitation is not established here. A GitHub repository is tagged as exploit-related, indicating public exploit research or tooling may exist, but the bundle does not prove in-the-wild exploitation.
Researcher notes
Key questions are kernel branch, CIFS client use, keyring/SPNEGO configuration, and vendor backport status. The source data confirms the fix logic but does not provide complete distro-by-distro exposure beyond Red Hat references.
Mitigation direction
Apply vendor kernel updates that include the cifs.spnego validation fix.
For Red Hat systems, review the listed RHSA advisories for applicable packages.
If patching is delayed, reduce local account access on affected Linux hosts.
Review whether CIFS/SMB client functionality is required on exposed multi-user systems.
Track upstream Linux stable commits referenced for fixed kernel branches.
Validation and detection
Inventory Linux kernel versions against the affected and fixed versions in vendor advisories.
Confirm whether cifs.upcall and SMB/CIFS mounts are present on target systems.
Verify patched kernels include the referenced cifs.spnego rejection change.
Check Red Hat CVE and errata status for each deployed product stream.
Prioritize validation on multi-user servers and workstation fleets with local users.
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.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
3CVSS vectors
5Timeline events
3ADP providers
43Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
3 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Expired Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.