CVE-2026-31626

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
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.1Exploit: None knownExposed: 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:

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify()

Initialize le_tmp64 to zero in rtw_BIP_verify() to prevent using uninitialized data.

Smatch warns that only 6 bytes are copied to this 8-byte (u64) variable, leaving the last two bytes uninitialized:

drivers/staging/rtl8723bs/core/rtw_security.c:1308 rtw_BIP_verify() warn: not copying enough bytes for '&le_tmp64' (8 vs 6 bytes)

Initializing the variable at the start of the function fixes this warning and ensures predictable behavior.

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

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (9)

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

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e911eead187240193516edf55a0e1ab3425aa5b
generic

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c964b82a4e97ec7f25e17b803ee196009b38a57
generic

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6792624d933146e2757b07092e93ad915cb58930
generic

staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51532c7c1d357145f4ac561648499f7a6847f739

Vendor Advisories for CVE-2026-31626(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.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 (129 versions)6.19.14-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 5× in last 7d / 32× 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 261 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31626?
CVE-2026-31626 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: initialize letmp64 in rtwBIP_verify() Initialize letmp64 to zero in rtwBIP_verify() to prevent using uninitialized data. Smatch warns that only 6 bytes are copied to this 8-byte (u64) variable, leaving the last…
When was CVE-2026-31626 disclosed?
CVE-2026-31626 was first published in the National Vulnerability Database on April 24, 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-31626 actively exploited?
CVE-2026-31626 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 78.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31626?
CVE-2026-31626 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31626?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31626, 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-31626

Explore →

Is Your Infrastructure Affected by CVE-2026-31626?

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

Start Free Scan →Browse All CVEs