CVE-2026-31552
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 6.1.170-1 |
| debian | bullseye | fixed | 6.1.170-1~deb11u1 |
| debian | forky | fixed | 6.19.10-1 |
| debian | sid | fixed | 6.19.10-1 |
| debian | trixie | fixed | 6.12.85-1 |
| linux-kernel | affected | 5.10.253 | |
| linux-kernel | 6.19 | affected | |
| linux-kernel | 7.0 | affected | |
References
- https://git.kernel.org/stable/c/12f9eef39e49716c763714bfda835a733d5f6dea
- https://git.kernel.org/stable/c/46c670ff1ff466e5eccb3940f726586473dc053c
- https://git.kernel.org/stable/c/980f793645540ca7a6318165cc12f49d5febeb99
- https://git.kernel.org/stable/c/a6dc74209462c4fe5a88718d2f3a5286886081c8
- https://git.kernel.org/stable/c/ceb46b40b021d21911ff8608ce4ed33c1264ad2f
- https://git.kernel.org/stable/c/cfa64e2b3717be1da7c4c1aff7268a009e8c1610
- https://git.kernel.org/stable/c/deb353d9bb009638b7762cae2d0b6e8fdbb41a69
- https://git.kernel.org/stable/c/f2c06d718a7b85cbc59ceaa2ff3f46b178ac709c
- https://www.suse.com/security/cve/CVE-2026-31552.html
- https://security-tracker.debian.org/tracker/CVE-2026-31552
CWEs
CWE-835
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.