Look up another CVE · open CVE-2026-98590 in the interactive tracker
CVE-2026-98590
bpf: Fix bpf_sock context code generation
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem net/core. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-98590 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.190-1 | Update the kernel and reboot. Fixed in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.113-1 | Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Currently, the ctx access code reads the rx_queue_mapping field with either a 4-byte or 2-byte load. The rest of the bits in the register are marked known zero by the verifier. However, the emitted ctx access code places in the register on certain the special value (-1) using BPF_MOV_IMM64, which gets sign-extended to turn on all the bits in the register. By shifting this value right, the program ends up with a value at runtime above what the verifier assumes is possible. Fix this by ensuring the read value is as wide as the assumed size. Use MOV32 instructions instead of MOV64 instructions to keep the upper bits zero as assumed by the verifier. Also properly report the size of the destination variable (the bpf_sock field, 4 bytes) instead of the source (the socket field, 2 bytes).
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
net/core/filter.c
- What this is
- BPF [GENERAL] (Safe Dynamic Programs and Tools)MAINTAINERS section matched on net/core/filter.c · bpf@vger.kernel.org · Supported
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS Debian linux-config packages
Signals
- Published
- 2026-10-18 (today)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- not scored
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- net/core
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.8 | 5.10.271 | e3ddcf4aeb34 |
| 5.8 | 5.15.222 | 4a41d064facc |
| 5.8 | 6.1.189 | 70288599d175 |
| 5.8 | 6.6.158 | ea4dc96c902c |
| 5.8 | 6.12.112 | b3f37afc7fd7 |
| 5.8 | 6.18.55 | d95dd5a6c6cd |
| 5.8 | 7.2.9 | 84ebb991ae98 |
| 5.8 | 7.3 | 4a4852376e3a |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98590, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.