# CVE-2026-98132: linux: In the Linux kernel, the following vulnerability has been resolved:  bpf: don't downgrade half-dead scalar zero spill...

CVE-2026-98132 is fixed in linux on 1 platform by DEBIAN-CVE-2026-98132 (version 7.2.7-1), released October 2, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-98132
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0011
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Sep 25, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  bpf: don't downgrade half-dead scalar zero spills to STACK_ZERO  states.c:__clean_func_state() can downgrade scalar zero spill to STACK_ZERO in the following case:    *(u64 *)(r10 - 8) = 0;   ... checkpoint ...   r1 = *(u32 *)(r10 - 4);   ... no reads from r10-8 ...  Here 4 bytes at r10-8 are dead and verifier changes scalar spill to a combination: 0000pppp (p stands for poison). Such a change breaks precision propagation chains. All places that produce STACK_ZERO should call bpf_mark_chain_precision() for the zero source.  This patch fixes the bug in a simplest way possible: avoids converting stack spills of zero to STACK_ZERO. Two smarter approaches are possible: - do bpf_mark_chain_precision() from __clean_func_state() - check slot liveness information in check_stack_write_fixed_off()  I investigated both and the changes required are a bit tricky, hence go with a simple fix for the time being.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.2.7-1 | [DEBIAN-CVE-2026-98132](https://patchblox.com/security/data/fix/linux/debian-cve-2026-98132.md) | Oct 2, 2026 |

---

Data as of 2026-11-09T01:18:40Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.