Skip to content
Noroxi
CVE-2022-49063· NVD / CVE Program· CNA Linux

ice: arfs: fix use-after-free when freeing @rx_cpu_rmap

Noroxi assessment

Priority: Monitor (action score 31/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.31% (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 618df75f2e30c7838a3e010ca32cd4893ec9fe33, ba2f6ec28733fb6b24ed086e676df3df4c138f3f, d08d2fb6d99d82da1c63aba5c0d1c6f237e150f3.

Low priority for now. Upgrade to Linux Linux 618df75f2e30c7838a3e010ca32cd4893ec9fe33, ba2f6ec28733fb6b24ed086e676df3df4c138f3f, d08d2fb6d99d82da1c63aba5c0d1c6f237e150f3 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: ice: arfs: fix use-after-free when freeing @rx_cpu_rmap The CI testing bots triggered the following splat: [ 718.203054] BUG: KASAN: use-after-free in free_irq_cpu_rmap+0x53/0x80 [ 718.206349] Read of size 4 at addr ffff8881bd127e00 by task sh/20834 [ 718.212852] CPU: 28 PID: 20834 Comm: sh Kdump: loaded Tainted: G S W IOE 5.17.0-rc8_nextqueue-devqueue-02643-g23f3121aca93 #1 [ 718.219695] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0012.070720200218 07/07/2020 [ 718.223418] Call Trace: [ 718.227139] [ 718.230783] dump_stack_lvl+0x33/0x42 [ 718.234431] print_address_description.constprop.9+0x21/0x170 [ 718.238177] ? free_irq_cpu_rmap+0x53/0x80 [ 718.241885] ? free_irq_cpu_rmap+0x53/0x80 [ 718.245539] kasan_report.cold.18+0x7f/0x11b [ 718.249197] ? free_irq_cpu_rmap+0x53/0x80 [ 718.252852] free_irq_cpu_rmap+0x53/0x80 [ 718.256471] ice_free_cpu_rx_rmap.part.11+0x37/0x50 [ice] [ 718.260174] ice_remove_arfs+0x5f/0x70 [ice] [ 718.263810] ice_rebuild_arfs+0x3b/0x70 [ice] [ 718.267419] ice_rebuild+0x39c/0xb60 [ice] [ 718.270974] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [ 718.274472] ? ice_init_phy_user_cfg+0x360/0x360 [ice] [ 718.278033] ? delay_tsc+0x4a/0xb0 [ 718.281513] ? preempt_count_sub+0x14/0xc0 [ 718.284984] ? delay_tsc+0x8f/0xb0 [ 718.288463] ice_do_reset+0x92/0xf0 [ice] [ 718.292014] ice_pci_err_resume+0x91/0xf0 [ice] [ 718.295561] pci_reset_function+0x53/0x80 <...> [ 718.393035] Allocated by task 690: [ 718.433497] Freed by task 20834: [ 718.495688] Last potentially related work creation: [ 718.568966] The buggy address belongs to the object at ffff8881bd127e00 which belongs to the cache kmalloc-96 of size 96 [ 718.574085] The buggy address is located 0 bytes inside of 96-byte region [ffff8881bd127e00, ffff8881bd127e60) [ 718.579265] The buggy address belongs to the page: [ 718.598905] Memory state around the buggy address: [ 718.601809] ffff8881bd127d00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc [ 718.604796] ffff8881bd127d80: 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc [ 718.607794] >ffff8881bd127e00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc [ 718.610811] ^ [ 718.613819] ffff8881bd127e80: 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc [ 718.617107] ffff8881bd127f00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc This is due to that free_irq_cpu_rmap() is always being called *after* (devm_)free_irq() and thus it tries to work with IRQ descs already freed. For example, on device reset the driver frees the rmap right before allocating a new one (the splat above). Make rmap creation and freeing function symmetrical with {request,free}_irq() calls i.e. do that on ifup/ifdown instead of device probe/remove/resume. These operations can be performed independently from the actual device aRFS configuration. Also, make sure ice_vsi_free_irq() clears IRQ affinity notifiers only when aRFS is disabled -- otherwise, CPU rmap sets and clears its own and they must not be touched manually.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 22th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

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-49063

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.

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
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.8 and later · before 5.10.238
  • linux linux kernel5.11 and later · before 5.15.184
  • linux linux kernel5.16 and later · before 5.17.4
  • linux linux kernel5.18

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.8affected
    • 28bf26724fdb0e02267d19e280d6717ee810a10d and later · before ba2f6ec28733fb6b24ed086e676df3df4c138f3faffected · git
    • 28bf26724fdb0e02267d19e280d6717ee810a10d and later · before 618df75f2e30c7838a3e010ca32cd4893ec9fe33affected · git
    • 28bf26724fdb0e02267d19e280d6717ee810a10d and later · before d08d2fb6d99d82da1c63aba5c0d1c6f237e150f3affected · git
    • 28bf26724fdb0e02267d19e280d6717ee810a10d and later · before d7442f512b71fc63a99c8a801422dde4fbbf9f93affected · git
    • before 5.8not affected · semver
    • 5.10.238 and later · up to and including 5.10.*not affected · semver
    • 5.15.184 and later · up to and including 5.15.*not affected · semver
    • 5.17.4 and later · up to and including 5.17.*not affected · semver
    • 5.18 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
Debian:11linuxbefore 5.10.244-15.10.244-1
Debian:12linuxbefore 5.17.6-15.17.6-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamperfbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreamperf-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::appstreampython3-perf-debuginfobefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::baseosbpftoolbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::baseoskernelbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0
Red Hat:enterprise_linux:9::baseoskernel-abi-stablelistsbefore 0:5.14.0-70.26.1.el9_00:5.14.0-70.26.1.el9_0

+15

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49061Feb 26, 2025 · net: ethernet: stmmac: fix altr_tse_pcs function when using a fixed-link
    22Monitor
  • ← EarlierCVE-2022-49062Feb 26, 2025 · cachefiles: Fix KASAN slab-out-of-bounds in cachefiles_set_volume_xattr
    31Monitor
  • Later →CVE-2022-49064Feb 26, 2025 · cachefiles: unmark inode in use in error path
    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 Linux618df75f2e30c7838a3e010ca32cd4893ec9fe33Vendor (CNA)
Linux Linuxba2f6ec28733fb6b24ed086e676df3df4c138f3fVendor (CNA)
Linux Linuxd08d2fb6d99d82da1c63aba5c0d1c6f237e150f3Vendor (CNA)
Linux Linuxd7442f512b71fc63a99c8a801422dde4fbbf9f93Vendor (CNA)
debian:linux5.17.6-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-x86_640:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-devel0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-devel-matched0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-doc0:5.14.0-70.26.1.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage 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.

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
high · data or configuration can be modified
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
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

All records