CVE-2026-31507

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: 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:

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer

smc_rx_splice() allocates one smc_spd_priv per pipe_buffer and stores the pointer in pipe_buffer.private. The pipe_buf_operations for these buffers used .get = generic_pipe_buf_get, which only increments the page reference count when tee(2) duplicates a pipe buffer. The smc_spd_priv pointer itself was not handled, so after tee() both the original and the cloned pipe_buffer share the same smc_spd_priv *.

When both pipes are subsequently released, smc_rx_pipe_buf_release() is called twice against the same object:

1st call: kfree(priv) sock_put(sk) smc_rx_update_cons() [correct] 2nd call: kfree(priv) sock_put(sk) smc_rx_update_cons() [UAF]

KASAN reports a slab-use-after-free in smc_rx_pipe_buf_release(), which then escalates to a NULL-pointer dereference and kernel panic via smc_rx_update_consumer() when it chases the freed priv->smc pointer:

BUG: KASAN: slab-use-after-free in smc_rx_pipe_buf_release+0x78/0x2a0 Read of size 8 at addr ffff888004a45740 by task smc_splice_tee_/74 Call Trace: dump_stack_lvl+0x53/0x70 print_report+0xce/0x650 kasan_report+0xc6/0x100 smc_rx_pipe_buf_release+0x78/0x2a0 free_pipe_info+0xd4/0x130 pipe_release+0x142/0x160 __fput+0x1c6/0x490 __x64_sys_close+0x4f/0x90 do_syscall_64+0xa6/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: kernel NULL pointer dereference, address: 0000000000000020 RIP: 0010:smc_rx_update_consumer+0x8d/0x350 Call Trace: smc_rx_pipe_buf_release+0x121/0x2a0 free_pipe_info+0xd4/0x130 pipe_release+0x142/0x160 __fput+0x1c6/0x490 __x64_sys_close+0x4f/0x90 do_syscall_64+0xa6/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f Kernel panic - not syncing: Fatal exception

Beyond the memory-safety problem, duplicating an SMC splice buffer is semantically questionable: smc_rx_update_cons() would advance the consumer cursor twice for the same data, corrupting receive-window accounting. A refcount on smc_spd_priv could fix the double-free, but the cursor-accounting issue would still need to be addressed separately.

The .get callback is invoked by both tee(2) and splice_pipe_to_pipe() for partial transfers; both will now return -EFAULT. Users who need to duplicate SMC socket data must use a copy-based read path.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
3.1%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 14, 2026

Advisory Details (8)

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

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98ba5cb274768146e25ffbfde47753652c1c20d3
generic

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81acbd345d405994875d419d43b319fee0b9ad62
generic

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e8916f46c2f48607f907fd401590093753a6bc5
generic

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bcb974c771c863e8588cea0012ac204443a7126
generic

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54c87a730157868543ebdfa0ecb21b4590ed23a5
generic

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3cc76380fea749280c026f410af56a28aaac388a
generic

net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24dd586bb4cbba1889a50abe74143817a095c1c9

Vendor Advisories for CVE-2026-31507(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 46× 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 160 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31507?
CVE-2026-31507 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net/smc: fix double-free of smcspdpriv when tee() duplicates splice pipe buffer smcrxsplice() allocates one smcspdpriv per pipe_buffer and stores the pointer in pipebuffer.private. The pipebuf_operations for these buffers used .get…
When was CVE-2026-31507 disclosed?
CVE-2026-31507 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31507 actively exploited?
CVE-2026-31507 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31507?
CVE-2026-31507 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31507?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31507, 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-31507

Explore →

Is Your Infrastructure Affected by CVE-2026-31507?

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

Start Free Scan →Browse All CVEs