CVE-2026-31408

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold

sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free.

Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock.

Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
21.9%
KEV
Not listed

Published

April 6, 2026

Last Modified

May 20, 2026

Advisory Details (7)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7197462e90b8ce15caa1ae15d4bc2bb8cd21b11e
generic

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/598dbba9919c5e36c54fe1709b557d64120cb94b
generic

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45aaca995e4a7a05b272a58e7ab2fff4f611b8f1
generic

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/108b81514d8f2535eb16651495cefb2250528db3

Vendor Advisories for CVE-2026-31408(13)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
redhatkernel-0:6.12.0-211.16.1.el10_22026-05-20redhat

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 10× in last 7d / 43× 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 119 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31408?
CVE-2026-31408 is a high vulnerability published on April 6, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix use-after-free in scorecvframe() due to missing sock_hold scorecvframe() reads conn->sk under scoconnlock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can…
When was CVE-2026-31408 disclosed?
CVE-2026-31408 was first published in the National Vulnerability Database on April 6, 2026, with the most recent update on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31408 actively exploited?
CVE-2026-31408 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31408?
CVE-2026-31408 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31408?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31408, 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-31408

Explore →

Is Your Infrastructure Affected by CVE-2026-31408?

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

Start Free Scan →Browse All CVEs