Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry

Noroxi assessment

Priority: Monitor (action score 39/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.46% (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 0e18641708eaa8bc3c1ff338cd844aeadbd52bac, 0fa8a8acae57e6373962741d5b06d13f44aba6a9, 11539e8fcce0b0af062ae5fecf7b3676c2f7aeed; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 0e18641708eaa8bc3c1ff338cd844aeadbd52bac, 0fa8a8acae57e6373962741d5b06d13f44aba6a9, 11539e8fcce0b0af062ae5fecf7b3676c2f7aeed; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.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: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry svcauth_gss_decode_credbody() writes the caller's rpc_gss_wire_cred field by field and assigns gc_ctx.len only on the success tail. The caller storage is svcdata->clcred, which lives in the per-svc_rqst gss_svc_data and is reused across requests. Early decode failures leave partially decoded state mixed with residue from the prior request. The trailing body_len tightness check is the sharpest case: xdr_stream_decode_opaque_inline() has already written gc_ctx.data with a borrowed inline pointer into the current request's XDR pages, but gc_ctx.len retains its prior value. Once the request pages are released the pooled clcred carries a dangling pointer paired with a stale length. Zero the caller's rpc_gss_wire_cred at function entry so that every early-return path leaves a deterministic all-zero cred. On the trailing tightness-check path, gc_ctx.len is now zero instead of stale, which neuters length-driven consumers such as gss_svc_searchbyctx() that would otherwise walk the dangling data pointer.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Sep 24, 2026
Updated
Oct 19, 2026
EPSS
0.4% · 40th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
—
CNA · Linux
9.8
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.

Follow CVE-2026-93207

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.

—

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
    • b0bc53470d1af01f62a0fe2d405cf56477804863 and later · before 56b29d62017c7dd1718d060dd5b3a2ce61095d0caffected · git
    • b0bc53470d1af01f62a0fe2d405cf56477804863 and later · before 0e18641708eaa8bc3c1ff338cd844aeadbd52bacaffected · git
    • b0bc53470d1af01f62a0fe2d405cf56477804863 and later · before e0778464049b0238f2915a40007a4154f86cf351affected · git
    • b0bc53470d1af01f62a0fe2d405cf56477804863 and later · before 0fa8a8acae57e6373962741d5b06d13f44aba6a9affected · git
    • b0bc53470d1af01f62a0fe2d405cf56477804863 and later · before 11539e8fcce0b0af062ae5fecf7b3676c2f7aeedaffected · git
    • before 6.3not affected · semver
    • 6.6.157 and later · up to and including 6.6.*not affected · semver
    • 6.12.109 and later · up to and including 6.12.*not affected · semver
    • 6.18.50 and later · up to and including 6.18.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93205Sep 24, 2026 · iommu/arm-smmu-v3: Manage teardown with devm
    0Monitor
  • ← EarlierCVE-2026-93206Sep 24, 2026 · PCI/proc: Use file_ns_capable() when checking config space read access
    0Monitor
  • Later →CVE-2026-93208Sep 24, 2026 · kasan: fix cache shrink race with CPU hotplug
    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 / packageFixed versionSource
Linux Linux0e18641708eaa8bc3c1ff338cd844aeadbd52bacVendor (CNA)
Linux Linux0fa8a8acae57e6373962741d5b06d13f44aba6a9Vendor (CNA)
Linux Linux11539e8fcce0b0af062ae5fecf7b3676c2f7aeedVendor (CNA)
Linux Linux56b29d62017c7dd1718d060dd5b3a2ce61095d0cVendor (CNA)
Linux Linuxe0778464049b0238f2915a40007a4154f86cf351Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.66.1.el10_2 · AlmaLinux:10Package registry (OSV)

+15

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records