- Exploited
- No known exploitation
- Fix
- Fixed in 7.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Linux kernel's ksmbd SMB server has a use-after-free flaw in how it tracks session channels: a connection can be freed while another session reference is still using it. The provided data does not state what an attacker can gain or how they would reach the flaw, so no attack vector can be described.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: hold a connection reference for each session channel
ksmbd_session_unregister() removes a session from the global and per- connection tables before dropping the table reference. A concurrent reference holder can keep the session and its channel list alive after those removals.
Connection cleanup can no longer find the unpublished session to remove its channels. Since a channel only stores a raw conn pointer, the connection can be freed while another session reference holder is still accessing it, for example during SMB3.1.1 binding or a procfs read.
Take a connection reference when registering a channel and release it on insertion failure, channel removal, or final session destruction. Keep the channels and signing keys until the session is destroyed so a response can still be signed after the session has been unregistered.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 7.2.8 · fixed in 7.3
- Linux Linux
7.3
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-99277
Is CVE-2026-99277 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-99277?
Linux: from 7.2.8 before 7.3. Linux: version 7.3.Source: cve.now feed data
How do I fix CVE-2026-99277?
Upgrade to a fixed version: 7.3.Source: cve.now feed data