Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93785: cifs: validate idmap key payload length

Noroxi assessment

Priority: Monitor (action score 0/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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 125b05ac8ca8758950e4369c1542d57a162f504c, 3a4a34a732e8a08309eed0a74314dbd9f2f1c972, 455488cd5054bcc59db40fa1cc2c004031a5b2a5; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 125b05ac8ca8758950e4369c1542d57a162f504c, 3a4a34a732e8a08309eed0a74314dbd9f2f1c972, 455488cd5054bcc59db40fa1cc2c004031a5b2a5; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: cifs: validate idmap key payload length The cifs.idmap key type stores its payload length in key->datalen, which is limited to U16_MAX. Accepting a larger key payload truncates the recorded length and can make later users interpret the payload using inconsistent bounds. Reject oversized preparsed payloads before allocating or copying them. This keeps key->datalen consistent with the stored data for both inline and separately allocated idmap payloads.

—No exploit Fix available
Published
Sep 24, 2026
Updated
Oct 3, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-93785

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.

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

    • 3.2affected
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before eeac976b74b4f697cfc517187b7cbfd72652dbbcaffected · git
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before 125b05ac8ca8758950e4369c1542d57a162f504caffected · git
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before 945f6cde6bcf8f08f6fa5df8882b1b9582e55efaaffected · git
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before 3a4a34a732e8a08309eed0a74314dbd9f2f1c972affected · git
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before 6cfeef221ac00d63c07f6122f58e6159bde69ca0affected · git
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before 8b12f65d7caf16d124098cb4895a203367d35b57affected · git
    • 21fed0d5b763b94a7d1568c27d0cce892ab8d43e and later · before 455488cd5054bcc59db40fa1cc2c004031a5b2a5affected · git
    • before 3.2not affected · semver
    • 5.10.271 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

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-93783Sep 24, 2026 · Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame
    0Monitor
  • ← EarlierCVE-2026-93784Sep 24, 2026 · wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie()
    0Monitor
  • Later →CVE-2026-93786Sep 24, 2026 · ksmbd: preserve VFS inherited POSIX ACL mask
    32Monitor

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 Linux125b05ac8ca8758950e4369c1542d57a162f504cVendor (CNA)
Linux Linux3a4a34a732e8a08309eed0a74314dbd9f2f1c972Vendor (CNA)
Linux Linux455488cd5054bcc59db40fa1cc2c004031a5b2a5Vendor (CNA)
Linux Linux6cfeef221ac00d63c07f6122f58e6159bde69ca0Vendor (CNA)
Linux Linux8b12f65d7caf16d124098cb4895a203367d35b57Vendor (CNA)
Linux Linux945f6cde6bcf8f08f6fa5df8882b1b9582e55efaVendor (CNA)
Linux Linuxeeac976b74b4f697cfc517187b7cbfd72652dbbcVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package 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.

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.

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

All records