CVE-2026-46098: net: caif: clear client service pointer on teardown
In the Linux kernel, the following vulnerability has been resolved:
net: caif: clear client service pointer on teardown
`caif_connect()` can tear down an existing client after remote shutdown by
calling `caif_disconnect_client()` followed by `caif_free_client()`.
`caif_free_client()` releases the service layer referenced by
`adap_layer->dn`, but leaves that pointer stale.
When the socket is later destroyed, `caif_sock_destructor()` calls
`caif_free_client()` again and dereferences the freed service pointer.
Clear the client/service links before releasing the service object so
repeated teardown becomes harmless.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel cleanup bug in the CAIF networking code. A service object can be freed during disconnect but left referenced, so later socket destruction can touch freed memory. Business impact is unclear because the CVE has no CVSS score, CWE, or cited active exploitation.
Executive priority
Monitor and patch through normal Linux kernel maintenance unless asset context raises risk. Escalate priority for shared hosts, systems with untrusted local users, or environments where kernel instability has high operational impact.
Technical view
The flaw is a stale pointer/use-after-free condition around caif_connect(), caif_disconnect_client(), caif_free_client(), and caif_sock_destructor(). The fix clears client and service links before releasing the service object, making repeated teardown harmless.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds where CAIF networking code is present and reachable. The source bundle lists Linux kernel versions and stable commits but does not identify distributions, default configurations, or package backports.
Exploitation context
The provided sources do not show public exploitation, weaponized exploit code, or KEV listing. Treat active exploitation as unsupported by current evidence. Kernel memory-safety bugs can still matter operationally, especially on shared or untrusted-user systems.
Researcher notes
Evidence supports a repeated teardown use-after-free in net/caif. The CVE record lacks CVSS, CWE, exploitability details, and distribution impact. Research should focus on reachability of CAIF socket paths in real deployments and whether downstream kernels backported the fix.
Mitigation direction
Check Linux kernel and distribution advisories for CVE-2026-46098 guidance.
Update to a kernel containing the referenced stable fix commits.
Prioritize internet-facing, multi-user, and high-trust Linux systems first.
Track vendor backports rather than relying only on upstream version strings.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Confirm whether vendor kernels include the referenced CAIF teardown fix.
Review kernel configuration and module exposure for CAIF networking support.
Retest after patching using standard regression and boot validation procedures.
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-46098 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
9Source 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.
May 27, 2026, 12:59 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.