CVE-2026-31552

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom

Since upstream commit e75665dd0968 ("wifi: wlcore: ensure skb headroom before skb_push"), wl1271_tx_allocate() and with it wl1271_prepare_tx_frame() returns -EAGAIN if pskb_expand_head() fails. However, in wlcore_tx_work_locked(), a return value of -EAGAIN from wl1271_prepare_tx_frame() is interpreted as the aggregation buffer being full. This causes the code to flush the buffer, put the skb back at the head of the queue, and immediately retry the same skb in a tight while loop.

Because wlcore_tx_work_locked() holds wl->mutex, and the retry happens immediately with GFP_ATOMIC, this will result in an infinite loop and a CPU soft lockup. Return -ENOMEM instead so the packet is dropped and the loop terminates.

The problem was found by an experimental code review agent based on gemini-3.1-pro while reviewing backports into v6.18.y.

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
39.9%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 27, 2026

Advisory Details (8)

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/980f793645540ca7a6318165cc12f49d5febeb99
generic

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46c670ff1ff466e5eccb3940f726586473dc053c
generic

wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12f9eef39e49716c763714bfda835a733d5f6dea

Vendor Advisories for CVE-2026-31552(1)

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.253osv

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

Frequently asked(5)

What is CVE-2026-31552?
CVE-2026-31552 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom Since upstream commit e75665dd0968 ("wifi: wlcore: ensure skb headroom before skbpush"), wl1271tx_allocate() and with it wl1271preparetxframe() returns…
When was CVE-2026-31552 disclosed?
CVE-2026-31552 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31552 actively exploited?
CVE-2026-31552 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31552?
CVE-2026-31552 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31552?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31552, 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-31552

Explore →

Is Your Infrastructure Affected by CVE-2026-31552?

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