CVE-2025-68246: ksmbd: close accepted socket when per-IP limit rejects connection
Noroxi assessment
Priority: Monitor (action score 30/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.41% (FIRST EPSS).
- 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.
- Fixed version: Linux Linux 35521b5a7e8a184548125f4530552101236dcda1, 4587a7826be1ae0190dba10ff70b46bb0e3bc7d3, 5746b2a0f5eb3d79667b3c51fe849bd62464220e.
Low priority for now. Upgrade to Linux Linux 35521b5a7e8a184548125f4530552101236dcda1, 4587a7826be1ae0190dba10ff70b46bb0e3bc7d3, 5746b2a0f5eb3d79667b3c51fe849bd62464220e 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: ksmbd: close accepted socket when per-IP limit rejects connection When the per-IP connection limit is exceeded in ksmbd_kthread_fn(), the code sets ret = -EAGAIN and continues the accept loop without closing the just-accepted socket. That leaks one socket per rejected attempt from a single IP and enables a trivial remote DoS. Release client_sk before continuing. This bug was found with ZeroPath.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- 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.15affected
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 7a3c7154d5fc05956a8ad9e72ecf49e21555bfcaaffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 5746b2a0f5eb3d79667b3c51fe849bd62464220eaffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 4587a7826be1ae0190dba10ff70b46bb0e3bc7d3affected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 35521b5a7e8a184548125f4530552101236dcda1affected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 98a5fd31cbf72d46bf18e50b3ab0ce86d5f319a9affected · git
- before 5.15not affected · semver
- 6.1.159 and later · up to and including 6.1.*not affected · semver
- 6.6.117 and later · up to and including 6.6.*not affected · semver
- 6.12.59 and later · up to and including 6.12.*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.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.9-1 | 6.17.9-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-2025-68243Dec 16, 2025 · NFS: Check the TLS certificate fields in nfs_match_client()28Monitor
- ← EarlierCVE-2025-68245Dec 16, 2025 · net: netpoll: fix incorrect refcount handling causing incorrect cleanup0Monitor
- Later →CVE-2025-68247Dec 16, 2025 · posix-timers: Plug potential memory leak in do_timer_create()0Monitor
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 | 35521b5a7e8a184548125f4530552101236dcda1 | Vendor (CNA) |
| Linux Linux | 4587a7826be1ae0190dba10ff70b46bb0e3bc7d3 | Vendor (CNA) |
| Linux Linux | 5746b2a0f5eb3d79667b3c51fe849bd62464220e | Vendor (CNA) |
| Linux Linux | 7a3c7154d5fc05956a8ad9e72ecf49e21555bfca | Vendor (CNA) |
| Linux Linux | 98a5fd31cbf72d46bf18e50b3ab0ce86d5f319a9 | Vendor (CNA) |
| debian:linux | 6.1.159-1 · 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.
No history yet (it accumulates with the daily EPSS job).
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).
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.