What is CVE-2026-98150?

CVE-2026-98150 is a High severity Linux kernel vulnerability with a CVSS score of 7.0 out of 10, affecting Linux kernel versions from 7.0 onward and patched in 7.2.7 and 7.3-rc2. CVE-2026-98150 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-98150?

CVE-2026-98150 has a CVSS score of 7.0 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-98150?

Yes, CVE-2026-98150 has been patched. Fixed versions include 7.2.7 and 7.3-rc2. If you are running Linux kernel 7.0 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-98150 actively exploited?

CVE-2026-98150 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-98150

High

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix BPF_F_CPU validation for sparse CPU IDs BPF_F_CPU stores the target CPU ID in the upper 32 bits of the map operation flags. bpf_map_check_op_flags() currently compares that ID with num_possible_cpus(), which is the number of possible CPUs rather than a bound on CPU IDs. On an arm64 QEMU guest with a CPU device-tree hole, the possible CPU mask was 0,2-3. A userspace program using raw bpf() syscalls creates a BPF_MAP_TYPE_PERCPU_ARRAY and performs update and lookup operations for each CPU by setting BPF_F_CPU and the CPU ID in the flags. With the old check, CPU 1 is incorrectly accepted while valid CPU 3 is rejected with -ERANGE. The CPU 1 update then reaches the per-CPU map access path and triggers: Unable to handle kernel paging request at virtual address ... pc : __pi_memcpy_generic+0x5c/0x22c lr : bpf_percpu_array_update+0x2dc/0x2e8 Call trace: __pi_memcpy_generic bpf_map_update_value map_update_elem __sys_bpf Check the CPU ID against nr_cpu_ids and cpu_possible() instead. This rejects CPU IDs outside the valid range and CPUs absent from the possible mask, while allowing valid sparse CPU IDs.

Package Linux Kernel

Published 2026-09-25

Last modified 2026-09-30

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.0

out of 10

High

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 7.0 and later are affected. Fixed in 7.2.7, 7.3-rc2 and their respective stable series.

Affected from

≥ 7.0

Fixed in

✓ 7.2.7 7.2.x ✓ 7.3-rc2

References

2 total

Details

CVE ID CVE-2026-98150

Severity High

CVSS score 7.0 / 10

CVSS version 3.1

Published 2026-09-25

Modified 2026-09-30

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-98150?

CVE-2026-98150 is a High severity Linux kernel vulnerability with a CVSS score of 7.0 out of 10 . It affects Linux kernel versions from 7.0 onward and has been patched in 7.2.7 and 7.3-rc2. CVE-2026-98150 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-98150?

CVE-2026-98150 has a CVSS score of 7.0 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-98150?

Yes. CVE-2026-98150 has been patched. Fixed versions include 7.2.7 and 7.3-rc2. If you are running Linux kernel 7.0 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-98150 actively exploited?

No. CVE-2026-98150 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.