CVE-2026-31535

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-04-24. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

smb: client: make use of smbdirect_socket.recv_io.credits.available

The logic off managing recv credits by counting posted recv_io and granted credits is racy.

That's because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the 'recv_done' functions we likely have a window where we grant credits, which don't really exist.

So we better have a decicated counter for the available credits, which will be incremented when we posted new recv buffers and drained when we grant the credits to the peer.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.5%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 28, 2026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.11osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-07-23 03:08 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-19 23:08 UTCOSV refresh
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 75 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-19 19:25 UTCEPSS rescore
  11. 2026-06-19 19:25 UTCEPSS rescore
  12. 2026-06-17 17:53 UTCEPSS rescore
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-14 23:18 UTCEPSS rescore
  16. 2026-06-14 12:03 UTCGHSA enrichment
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-11 14:06 UTCGHSA enrichment
  21. 2026-06-11 14:00 UTCEPSS rescore
  22. 2026-06-10 22:18 UTCEPSS rescore
  23. 2026-06-10 13:45 UTCGHSA enrichment
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-09 13:48 UTCGHSA enrichment
  26. 2026-06-08 14:17 UTCEPSS rescore
  27. 2026-06-08 14:17 UTCEPSS rescore
  28. 2026-06-08 13:52 UTCGHSA enrichment
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 15:25 UTCEPSS rescore
  32. 2026-06-07 13:45 UTCGHSA enrichment
  33. 2026-06-06 13:48 UTCGHSA enrichment
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 13:47 UTCEPSS rescore
  36. 2026-06-05 22:47 UTCEPSS rescore
  37. 2026-06-05 22:47 UTCEPSS rescore
  38. 2026-06-05 13:52 UTCGHSA enrichment
  39. 2026-06-05 06:10 UTCEPSS rescore
  40. 2026-06-05 06:10 UTCEPSS rescore
  41. 2026-06-04 13:39 UTCGHSA enrichment
  42. 2026-06-04 13:12 UTCEPSS rescore
  43. 2026-06-04 13:12 UTCEPSS rescore
  44. 2026-06-03 13:41 UTCGHSA enrichment
  45. 2026-06-02 20:13 UTCEPSS rescore
  46. 2026-06-02 20:13 UTCEPSS rescore
  47. 2026-06-02 13:36 UTCGHSA enrichment
  48. 2026-06-01 13:51 UTCEPSS rescore
  49. 2026-06-01 13:51 UTCEPSS rescore
  50. 2026-06-01 13:39 UTCGHSA enrichment
  51. 2026-05-31 22:30 UTCEPSS rescore
  52. 2026-05-31 22:30 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-31 00:16 UTCEPSS rescore
  55. 2026-05-29 13:44 UTCEPSS rescore
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-28 13:44 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-27 13:40 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-26 13:44 UTCEPSS rescore
  64. 2026-05-26 13:44 UTCEPSS rescore
  65. 2026-05-26 07:18 UTCEPSS rescore
  66. 2026-05-26 07:18 UTCEPSS rescore
  67. 2026-05-26 07:18 UTCEPSS rescore
  68. 2026-05-23 15:21 UTCEPSS rescore
  69. 2026-05-22 21:16 UTCEPSS rescore
  70. 2026-05-20 22:38 UTCEPSS rescore
  71. 2026-05-20 22:38 UTCEPSS rescore
  72. 2026-05-20 22:37 UTCEPSS rescore
  73. 2026-05-20 15:54 UTCEG score recompute
  74. 2026-05-20 15:54 UTCGHSA enrichment
  75. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31535?
CVE-2026-31535 is a medium vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: make use of smbdirectsocket.recvio.credits.available The logic off managing recv credits by counting posted recv_io and granted credits is racy. That's because the peer might already consumed a credit, but between…
When was CVE-2026-31535 disclosed?
CVE-2026-31535 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31535 actively exploited?
CVE-2026-31535 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31535?
CVE-2026-31535 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-31535?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31535, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-31535

Explore →

Is Your Infrastructure Affected by CVE-2026-31535?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.