CVE-2026-89636: smb: client: clear ce->tgthint in free_tgts()
Noroxi assessment
Priority: Monitor (action score 39/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.66% (FIRST EPSS); higher than 51.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 14f60e959b5ac813715ff72e127beb3584ddabf6, 3ff9462bb7a06d8d32a1dc02d39580b078ec9e55, 5baab40404a9393bcc0b7b8f1950bf2c307e0984.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 14f60e959b5ac813715ff72e127beb3584ddabf6, 3ff9462bb7a06d8d32a1dc02d39580b078ec9e55, 5baab40404a9393bcc0b7b8f1950bf2c307e0984 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: smb: client: clear ce->tgthint in free_tgts() When free_tgts() frees all structures in ce->tlist, ce->tgthint is left pointing to one of the freed cache_dfs_tgt structures. If ce->tgthint is not reset before it is used later, it results in a use-after-free. Set ce->tgthint to NULL in free_tgts() after the elements are freed to reflect that no elements remain.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 5.0affected
- 54be1f6c1c37498bba557049df646cc239fa37e3 and later · before 14f60e959b5ac813715ff72e127beb3584ddabf6affected · git
- 54be1f6c1c37498bba557049df646cc239fa37e3 and later · before 3ff9462bb7a06d8d32a1dc02d39580b078ec9e55affected · git
- 54be1f6c1c37498bba557049df646cc239fa37e3 and later · before 7507bd1885643d0461a6017767492450af1ce2a3affected · git
- 54be1f6c1c37498bba557049df646cc239fa37e3 and later · before 9ab46a13798a61d9d020b01d4e57efdabe6624faaffected · git
- 54be1f6c1c37498bba557049df646cc239fa37e3 and later · before 5baab40404a9393bcc0b7b8f1950bf2c307e0984affected · git
- 54be1f6c1c37498bba557049df646cc239fa37e3 and later · before b1b741cf8e7ce1b91d937e23decd3d3358748700affected · git
- before 5.0not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*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 |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89634Sep 11, 2026 · smb: client: fix ALIGN() overflow in symlink_data() error context loop36Monitor
- ← EarlierCVE-2026-89635Sep 11, 2026 · ksmbd: only rebind the reopened file's own oplock on durable reconnect39Monitor
- Later →CVE-2026-89637Sep 11, 2026 · smb: client: fix UAF and buffer leak in cifs_check_trans2() for malformed secondary T239Monitor
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 | 14f60e959b5ac813715ff72e127beb3584ddabf6 | Vendor (CNA) |
| Linux Linux | 3ff9462bb7a06d8d32a1dc02d39580b078ec9e55 | Vendor (CNA) |
| Linux Linux | 5baab40404a9393bcc0b7b8f1950bf2c307e0984 | Vendor (CNA) |
| Linux Linux | 7507bd1885643d0461a6017767492450af1ce2a3 | Vendor (CNA) |
| Linux Linux | 9ab46a13798a61d9d020b01d4e57efdabe6624fa | Vendor (CNA) |
| Linux Linux | b1b741cf8e7ce1b91d937e23decd3d3358748700 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/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 (5 more)Show less
- git.kernel.org/stable/c/3ff9462bb7a06d8d32a1dc02d39580b078ec9e55
- git.kernel.org/stable/c/5baab40404a9393bcc0b7b8f1950bf2c307e0984
- git.kernel.org/stable/c/7507bd1885643d0461a6017767492450af1ce2a3
- git.kernel.org/stable/c/9ab46a13798a61d9d020b01d4e57efdabe6624fa
- git.kernel.org/stable/c/b1b741cf8e7ce1b91d937e23decd3d3358748700
Vendor advisories and official records. Exploit/PoC links are deliberately left out.