Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38089: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error

MediumCVSS 5.5 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.56% (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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 353e75b55e583635bf71cde6abcec274dba05edd, 599c489eea793821232a2f69a00fa57d82b0ac98, 6.4.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 353e75b55e583635bf71cde6abcec274dba05edd, 599c489eea793821232a2f69a00fa57d82b0ac98, 6.4 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: handle SVC_GARBAGE during svc auth processing as auth error tianshuo han reported a remotely-triggerable crash if the client sends a kernel RPC server a specially crafted packet. If decoding the RPC reply fails in such a way that SVC_GARBAGE is returned without setting the rq_accept_statp pointer, then that pointer can be dereferenced and a value stored there. If it's the first time the thread has processed an RPC, then that pointer will be set to NULL and the kernel will crash. In other cases, it could create a memory scribble. The server sunrpc code treats a SVC_GARBAGE return from svc_authenticate or pg_authenticate as if it should send a GARBAGE_ARGS reply. RFC 5531 says that if authentication fails that the RPC should be rejected instead with a status of AUTH_ERR. Handle a SVC_GARBAGE return as an AUTH_ERROR, with a reason of AUTH_BADCRED instead of returning GARBAGE_ARGS in that case. This sidesteps the whole problem of touching the rpc_accept_statp pointer in this situation and avoids the crash.

Published
Jun 30, 2025
Updated
Oct 15, 2026
EPSS
0.5% · 47th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
9.8
4.3 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38089

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

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

    • 9b59f5c4911e87264507e0934cd2bb277390c560, 6.4affected
    • 29cd2927fb914cc53b5ba4f67d2b74695c994ba4 and later · before 599c489eea793821232a2f69a00fa57d82b0ac98affected · git
    • 29cd2927fb914cc53b5ba4f67d2b74695c994ba4 and later · before 353e75b55e583635bf71cde6abcec274dba05eddaffected · git
    • 29cd2927fb914cc53b5ba4f67d2b74695c994ba4 and later · before c90459cd58bb421d275337093d8e901e0ba748ddaffected · git
    • 29cd2927fb914cc53b5ba4f67d2b74695c994ba4 and later · before 94d10a4dba0bc482f2b01e39f06d5513d0f75742affected · git
    • 6.3.4 and later · before 6.4affected · semver
    • before 6.4not affected · semver
    • 6.6.95 and later · up to and including 6.6.*not affected · semver
    • 6.12.35 and later · up to and including 6.12.*not affected · semver
    • 6.15.4 and later · up to and including 6.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.22.1.el10_06.12.0-55.22.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.22.1.el10_06.12.0-55.22.1.el10_0
AlmaLinux:9kernelbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.28.1.el9_65.14.0-570.28.1.el9_6

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38088Jun 30, 2025 · powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap
    28Monitor
  • ← EarlierCVE-2025-38090Jun 30, 2025 · drivers/rapidio/rio_cm.c: prevent possible heap overwrite
    22Monitor
  • Later →CVE-2025-38091Jul 2, 2025 · drm/amd/display: check stream id dml21 wrapper to get plane_id
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux353e75b55e583635bf71cde6abcec274dba05eddVendor (CNA)
Linux Linux599c489eea793821232a2f69a00fa57d82b0ac98Vendor (CNA)
Linux Linux6.4Vendor (CNA)
Linux Linux94d10a4dba0bc482f2b01e39f06d5513d0f75742Vendor (CNA)
Linux Linuxc90459cd58bb421d275337093d8e901e0ba748ddVendor (CNA)
almalinux:kernel5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.28.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.35-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.28.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+13

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:82025-07-02

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.

  1. Published
  2. First PoC+2 d
  3. TodayNov 13, 2026+501 d

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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
none
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
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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.

References

All records