CVE-2025-40084: ksmbd: transport_ipc: validate payload size before reading handle
Noroxi assessment
Priority: Monitor (action score 28/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.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2dc125f5da134c0915a840b62565c60a595673dd, 6f40e50ceb99fc8ef37e5c56e2ec1d162733fef0, 867ffd9d67285612da3f0498ca618297f8e41f01; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.
Low priority for now. Upgrade to Linux Linux 2dc125f5da134c0915a840b62565c60a595673dd, 6f40e50ceb99fc8ef37e5c56e2ec1d162733fef0, 867ffd9d67285612da3f0498ca618297f8e41f01; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1 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: transport_ipc: validate payload size before reading handle handle_response() dereferences the payload as a 4-byte handle without verifying that the declared payload size is at least 4 bytes. A malformed or truncated message from ksmbd.mountd can lead to a 4-byte read past the declared payload size. Validate the size before dereferencing. This is a minimal fix to guard the initial handle read.
- Published
- Oct 29, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- 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 a02e432d5130da4c723aabe1205bac805889fdb2affected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 2dc125f5da134c0915a840b62565c60a595673ddaffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 898d527ed94c19980a4d848f10057f1fed578ffbaffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 867ffd9d67285612da3f0498ca618297f8e41f01affected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 6f40e50ceb99fc8ef37e5c56e2ec1d162733fef0affected · git
- before 5.15not affected · semver
- 6.1.158 and later · up to and including 6.1.*not affected · semver
- 6.6.115 and later · up to and including 6.6.*not affected · semver
- 6.12.56 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.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.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-2023-7324Oct 29, 2025 · scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses32Monitor
- ← EarlierCVE-2025-40083Oct 29, 2025 · net/sched: sch_qfq: Fix null-deref in agg_dequeue0Monitor
- Later →CVE-2025-40085Oct 29, 2025 · ALSA: usb-audio: Fix NULL pointer deference in try_to_register_card0Monitor
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 | 2dc125f5da134c0915a840b62565c60a595673dd | Vendor (CNA) |
| Linux Linux | 6f40e50ceb99fc8ef37e5c56e2ec1d162733fef0 | Vendor (CNA) |
| Linux Linux | 867ffd9d67285612da3f0498ca618297f8e41f01 | Vendor (CNA) |
| Linux Linux | 898d527ed94c19980a4d848f10057f1fed578ffb | Vendor (CNA) |
| Linux Linux | a02e432d5130da4c723aabe1205bac805889fdb2 | Vendor (CNA) |
| azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 | 6.6.117.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.158-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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.