CVE-2025-40129: sunrpc: fix null pointer dereference on zero-length checksum
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.56% (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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 6df164e29bd4e6505c5a2e0e5f1e1f6957a16a42, 81cec07d303186d0d8c623ef8b5ecd3b81e94cf6, ab9a70cd2386a0d70c164b0905dd66bc9af52e77.
Low priority for now. Upgrade to Linux Linux 6df164e29bd4e6505c5a2e0e5f1e1f6957a16a42, 81cec07d303186d0d8c623ef8b5ecd3b81e94cf6, ab9a70cd2386a0d70c164b0905dd66bc9af52e77 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: sunrpc: fix null pointer dereference on zero-length checksum In xdr_stream_decode_opaque_auth(), zero-length checksum.len causes checksum.data to be set to NULL. This triggers a NPD when accessing checksum.data in gss_krb5_verify_mic_v2(). This patch ensures that the value of checksum.len is not less than XDR_UNIT.
- BDU:2025-15301
- SUSE-SU-2026:0487-1
- SUSE-SU-2026:0489-1
- SUSE-SU-2026:0490-1
- SUSE-SU-2026:0491-1
- SUSE-SU-2026:0543-1
- SUSE-SU-2026:0546-1
- SUSE-SU-2026:0548-1
- SUSE-SU-2026:0550-1
- SUSE-SU-2026:0551-1
- SUSE-SU-2026:0554-1
- SUSE-SU-2026:0555-1
- SUSE-SU-2026:0556-1
- SUSE-SU-2026:0557-1
- SUSE-SU-2026:0560-1
- SUSE-SU-2026:0561-1
- SUSE-SU-2026:20455-1
- SUSE-SU-2026:20456-1
- SUSE-SU-2026:20457-1
- SUSE-SU-2026:20458-1
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.5% · 46th 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.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
- 6.3affected
- 0653028e8f1c97fec30710813a001ad8a2ec34f4 and later · before 81cec07d303186d0d8c623ef8b5ecd3b81e94cf6affected · git
- 0653028e8f1c97fec30710813a001ad8a2ec34f4 and later · before affc03d44921f493deaae1d33151e3067a6f9f8faffected · git
- 0653028e8f1c97fec30710813a001ad8a2ec34f4 and later · before ab9a70cd2386a0d70c164b0905dd66bc9af52e77affected · git
- 0653028e8f1c97fec30710813a001ad8a2ec34f4 and later · before 6df164e29bd4e6505c5a2e0e5f1e1f6957a16a42affected · git
- before 6.3not affected · semver
- 6.6.112 and later · up to and including 6.6.*not affected · semver
- 6.12.53 and later · up to and including 6.12.*not affected · semver
- 6.17.3 and later · up to and including 6.17.*not affected · semver
- 6.18 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_10 | before 12-150600.2.1 | 12-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_13 | before 10-150600.2.1 | 10-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_14 | before 6-150600.2.1 | 6-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_15 | before 6-150600.2.1 | 6-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_7 | before 18-150600.2.1 | 18-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_8 | before 13-150600.2.1 | 13-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_0 | before 10-150700.3.27.1 | 10-150700.3.27.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_1 | before 10-150700.2.1 | 10-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_2 | before 10-150700.2.1 | 10-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_3 | before 6-150700.2.1 | 6-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_4 | before 6-150700.2.1 | 6-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_5 | before 3-150700.2.1 | 3-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_1 | before 10-150700.2.1 | 10-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_2 | before 10-150700.2.1 | 10-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_3 | before 6-150700.2.1 | 6-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_4 | before 6-150700.2.1 | 6-150700.2.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-livepatch-SLE16_Update_0 | before 7-160000.4.3 | 7-160000.4.3 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_10 | before 6-1.1 | 6-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_11 | before 5-1.1 | 5-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_12 | before 5-1.1 | 5-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_13 | before 3-1.1 | 3-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_4 | before 17-1.2 | 17-1.2 |
+14
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-40126Nov 12, 2025 · sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC0Monitor
- ← EarlierCVE-2025-40127Nov 12, 2025 · hwrng: ks-sa - fix division by zero in ks_sa_rng_init0Monitor
- Later →CVE-2025-40130Nov 12, 2025 · scsi: ufs: core: Fix data race in CPU latency PM QoS request handling0Monitor
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 | 6df164e29bd4e6505c5a2e0e5f1e1f6957a16a42 | Vendor (CNA) |
| Linux Linux | 81cec07d303186d0d8c623ef8b5ecd3b81e94cf6 | Vendor (CNA) |
| Linux Linux | ab9a70cd2386a0d70c164b0905dd66bc9af52e77 | Vendor (CNA) |
| Linux Linux | affc03d44921f493deaae1d33151e3067a6f9f8f | Vendor (CNA) |
| debian:linux | 6.12.57-1 · Debian:13 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_10 | 12-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_13 | 10-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_14 | 6-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_15 | 6-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_7 | 18-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_8 | 13-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_0 | 10-150700.3.27.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_3 | 6-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_1 | 10-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_2 | 10-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_3 | 6-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_4 | 6-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | 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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.