CVE-2026-31676

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-25. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

rxrpc: only handle RESPONSE during service challenge

Only process RESPONSE packets while the service connection is still in RXRPC_CONN_SERVICE_CHALLENGING. Check that state under state_lock before running response verification and security initialization, then use a local secured flag to decide whether to queue the secured-connection work after the state transition. This keeps duplicate or late RESPONSE packets from re-running the setup path and removes the unlocked post-transition state test.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

April 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d0035e634dae83237ab7f5681eb52b2f65d0ceb8
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c43ffdcfdbb5567b1f143556df8a04b4eeea041c
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6bcf8010af093fe04f7100562e9542ab7882585
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a1a8efde03a40b6c658d580e96644d9b9a2a0d3a
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c3a0fbdafef8316e34ae22333e317a341e737cd
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/29b44d904dceb832be880def08b8cb17a0aba91c
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0afdfd4941c1b60a1f5c361760daa970edca60cd
generic

rxrpc: only handle RESPONSE during service challenge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03fd2ef73cb4ffd0af100a95b634af54f474414e

Vendor Advisories for CVE-2026-31676(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-35.35) @ questing2026-06-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-124.124) @ noble2026-06-14ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1018.19) @ questing2026-06-14ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-14ubuntu
linuxKernel @ 5.10.258—osv

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.13-1—

Additional Vendor Advisories

(18)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 71× 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 260 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31676?
CVE-2026-31676 is a high vulnerability published on April 25, 2026. In the Linux kernel, the following vulnerability has been resolved: rxrpc: only handle RESPONSE during service challenge Only process RESPONSE packets while the service connection is still in RXRPCCONNSERVICECHALLENGING. Check that state under statelock before running response verification and…
When was CVE-2026-31676 disclosed?
CVE-2026-31676 was first published in the National Vulnerability Database on April 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31676 actively exploited?
CVE-2026-31676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.0% of all scored CVEs.
What is the CVSS score of CVE-2026-31676?
CVE-2026-31676 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31676?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31676, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31676

Explore →

Is Your Infrastructure Affected by CVE-2026-31676?

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

Start Free Scan →Browse All CVEs