Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31552, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.50% · top 56% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 88295a55fefe5414e64293638b6f7549646e58ed – < 980f793645540ca7a6318165cc12f49d5febeb99
    • affected cd89a4656c03f8db0c57350aaec69cd3cfaa3522 – < 12f9eef39e49716c763714bfda835a733d5f6dea
    • affected 745a0810dbc96a0471e5f5e627ba1e978c3116d4 – < ceb46b40b021d21911ff8608ce4ed33c1264ad2f
    • affected b167312390fdd461c81ead516f2b0b44e83a9edb – < a6dc74209462c4fe5a88718d2f3a5286886081c8
    • affected 71de0b6e04bbee5575caf9a1e4d424e7dcc50018 – < cfa64e2b3717be1da7c4c1aff7268a009e8c1610
    • affected 689a7980e4788e13e766763d53569fb78dea2513 – < 46c670ff1ff466e5eccb3940f726586473dc053c
    • affected e75665dd096819b1184087ba5718bd93beafff51 – < f2c06d718a7b85cbc59ceaa2ff3f46b178ac709c
    • affected e75665dd096819b1184087ba5718bd93beafff51 – < deb353d9bb009638b7762cae2d0b6e8fdbb41a69
    • affected 5.10.250 – < 5.10.253
    • affected 5.15.200 – < 5.15.203
    • affected 6.1.163 – < 6.1.167
    • affected 6.6.124 – < 6.6.130
    • affected 6.12.70 – < 6.12.78
    • affected 6.18.10 – < 6.18.20
  • Linux · Linux

    • affected 6.19
    • unaffected < 6.19
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.20 – ≤ 6.18.*
    • unaffected 6.19.10 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31552 badge
[![CVE-2026-31552](https://cveledger.app/badge/CVE-2026-31552.svg)](https://cveledger.app/cve/CVE-2026-31552)

Record last updated .