Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49985: bpf: Don't use tnum_range on array range checking for poke descriptors

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4f672112f8665102a5842c170be1713f8ff95919, a36df92c7ff7ecde2fb362241d0ab024dddd0597, a657182a5c5150cdfacb6640aad1d2712571a409.

Low priority for now. Upgrade to Linux Linux 4f672112f8665102a5842c170be1713f8ff95919, a36df92c7ff7ecde2fb362241d0ab024dddd0597, a657182a5c5150cdfacb6640aad1d2712571a409 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: bpf: Don't use tnum_range on array range checking for poke descriptors Hsin-Wei reported a KASAN splat triggered by their BPF runtime fuzzer which is based on a customized syzkaller: BUG: KASAN: slab-out-of-bounds in bpf_int_jit_compile+0x1257/0x13f0 Read of size 8 at addr ffff888004e90b58 by task syz-executor.0/1489 CPU: 1 PID: 1489 Comm: syz-executor.0 Not tainted 5.19.0 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x9c/0xc9 print_address_description.constprop.0+0x1f/0x1f0 ? bpf_int_jit_compile+0x1257/0x13f0 kasan_report.cold+0xeb/0x197 ? kvmalloc_node+0x170/0x200 ? bpf_int_jit_compile+0x1257/0x13f0 bpf_int_jit_compile+0x1257/0x13f0 ? arch_prepare_bpf_dispatcher+0xd0/0xd0 ? rcu_read_lock_sched_held+0x43/0x70 bpf_prog_select_runtime+0x3e8/0x640 ? bpf_obj_name_cpy+0x149/0x1b0 bpf_prog_load+0x102f/0x2220 ? __bpf_prog_put.constprop.0+0x220/0x220 ? find_held_lock+0x2c/0x110 ? __might_fault+0xd6/0x180 ? lock_downgrade+0x6e0/0x6e0 ? lock_is_held_type+0xa6/0x120 ? __might_fault+0x147/0x180 __sys_bpf+0x137b/0x6070 ? bpf_perf_link_attach+0x530/0x530 ? new_sync_read+0x600/0x600 ? __fget_files+0x255/0x450 ? lock_downgrade+0x6e0/0x6e0 ? fput+0x30/0x1a0 ? ksys_write+0x1a8/0x260 __x64_sys_bpf+0x7a/0xc0 ? syscall_enter_from_user_mode+0x21/0x70 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f917c4e2c2d The problem here is that a range of tnum_range(0, map->max_entries - 1) has limited ability to represent the concrete tight range with the tnum as the set of resulting states from value + mask can result in a superset of the actual intended range, and as such a tnum_in(range, reg->var_off) check may yield true when it shouldn't, for example tnum_range(0, 2) would result in 00XX -> v = 0000, m = 0011 such that the intended set of {0, 1, 2} is here represented by a less precise superset of {0, 1, 2, 3}. As the register is known const scalar, really just use the concrete reg->var_off.value for the upper index check.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
7.1
CNA · Linux
7.8
0.7 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49985

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.5 and later · before 5.10.140
  • linux linux kernel5.11 and later · before 5.15.64
  • linux linux kernel5.16 and later · before 5.19.6
  • linux linux kernel6.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.5affected
    • d2e4c1e6c2947269346054ac8937ccfe9e0bcc6b and later · before e8979807178434db8ceaa84dfcd44363e71e50bbaffected · git
    • d2e4c1e6c2947269346054ac8937ccfe9e0bcc6b and later · before 4f672112f8665102a5842c170be1713f8ff95919affected · git
    • d2e4c1e6c2947269346054ac8937ccfe9e0bcc6b and later · before a36df92c7ff7ecde2fb362241d0ab024dddd0597affected · git
    • d2e4c1e6c2947269346054ac8937ccfe9e0bcc6b and later · before a657182a5c5150cdfacb6640aad1d2712571a409affected · git
    • before 5.5not affected · semver
    • 5.10.140 and later · up to and including 5.10.*not affected · semver
    • 5.15.64 and later · up to and including 5.15.*not affected · semver
    • 5.19.6 and later · up to and including 5.19.*not affected · semver
    • 6.0 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.74.1.el8_104.18.0-553.74.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.74.1.rt7.415.el8_104.18.0-553.74.1.rt7.415.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49983Jun 18, 2025 · udmabuf: Set the DMA mask for the udmabuf device (v2)
    22Monitor
  • ← EarlierCVE-2022-49984Jun 18, 2025 · HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
    22Monitor
  • Later →CVE-2022-49986Jun 18, 2025 · scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4f672112f8665102a5842c170be1713f8ff95919Vendor (CNA)
Linux Linuxa36df92c7ff7ecde2fb362241d0ab024dddd0597Vendor (CNA)
Linux Linuxa657182a5c5150cdfacb6640aad1d2712571a409Vendor (CNA)
Linux Linuxe8979807178434db8ceaa84dfcd44363e71e50bbVendor (CNA)
almalinux:bpftool4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.74.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-553.74.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
rocky linux:kernel0:4.18.0-553.74.1.el8_10 · Rocky Linux:8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records