CVE-2026-98627
Last modified
CVE-2026-98627 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: bpf: Preserve packet pointer class displacement in regsafe() regsafe() maps packet pointer IDs between states and checks that each current register range is a subset of the corresponding explored register range. It does not, however, preserve the displacement between registers that share a packet pointer ID. This is unsound because packet range is shared by ID.
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Preserve packet pointer class displacement in regsafe() regsafe() maps packet pointer IDs between states and checks that each current register range is a subset of the corresponding explored register range. It does not, however, preserve the displacement between registers that share a packet pointer ID. This is unsound because packet range is shared by ID. A bounds check on one class member updates every member, and a later access can consume the range through another member. Commit 022ac0750883 ("bpf: use reg->var_off instead of reg->off for pointers") folded the fixed pointer offset into r64 and removed the old off equality check, so two individually narrower registers can prune even when their displacement has changed. The explored path can then license an out-of-bounds packet access on the pruned path. Require matching range bases for packet pointers with an ID. Together with the existing ID mapping, this preserves the displacement between members of each packet-pointer class without adding per-ID state. Packet pointers without an ID remain unaffected.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 022ac075088366b62e130da5e1b200bc93a47191, < 091b40845bd3cf96791171ca95113e9184ccb596; >= 022ac075088366b62e130da5e1b200bc93a47191, < fd16449a9b3b31a8f18944c2f0e29e4e218ca2cf |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98627?
How severe is CVE-2026-98627?
How do I fix CVE-2026-98627?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98621In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98622In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98623In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98624In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98625In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98626In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98628In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98629In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9863Fortra BoKS Manager contains an OS command injection vulnera…8.8
- CVE-2026-98630In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98631In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98632In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98627?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
