CVE-2022-49063: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2022-49063 is a high-severity use-after-free vulnerability in the Linux kernel affecting the ice network driver, specifically in the handling of IRQ (interrupt request) CPU rmap structures related to the aRFS (accelerated Receive Flow Steering) feature. The vulnerability arises because the function free_irq_cpu_rmap() is called after (devm_)free_irq(), causing it to operate on IRQ descriptors that have already been freed. This improper ordering leads to a use-after-free condition, which is a type of memory corruption where the kernel attempts to access memory that has been released back to the system. The issue was identified through kernel address sanitizer (KASAN) reports triggered by continuous integration testing bots, showing a BUG report with a stack trace pointing to free_irq_cpu_rmap() and related ice driver functions such as ice_remove_arfs and ice_rebuild_arfs. The root cause is that the rmap creation and freeing functions were not symmetrical with the request/free_irq() calls, being performed on device probe/remove/resume instead of on network interface up/down events. This mismatch allows for scenarios, such as device resets, where the rmap is freed prematurely before a new allocation, leading to the use-after-free. The fix involves aligning the lifecycle of the rmap with IRQ request/free calls and ensuring that IRQ affinity notifiers are only cleared when aRFS is disabled, preventing manual interference with CPU rmap sets. The vulnerability impacts Linux kernel versions containing the affected ice driver code, and it has a CVSS 3.1 score of 7.8, indicating high severity with potential for local privilege escalation or denial of service due to corrupted kernel memory. Exploitation requires local privileges but no user interaction, and the vulnerability affects confidentiality, integrity, and availability of the system. No known exploits are reported in the wild as of the publication date.
Potential Impact
For European organizations, this vulnerability poses a significant risk especially to environments running Linux servers with Intel Ethernet controllers using the ice driver, common in data centers, cloud infrastructure, and enterprise networks. Successful exploitation could allow an attacker with local access to cause kernel crashes (denial of service) or potentially escalate privileges by corrupting kernel memory, undermining system integrity and confidentiality. This is particularly critical for sectors relying on high availability and secure data processing such as finance, healthcare, telecommunications, and government institutions. The vulnerability could disrupt critical services and lead to data breaches or system downtime. Given the widespread use of Linux in European IT infrastructure, especially in cloud and virtualization platforms, the impact could be broad if not mitigated promptly.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to versions where this vulnerability is patched. Since the issue is in the ice network driver, organizations should audit their systems to identify usage of Intel Ethernet adapters relying on this driver. Network administrators should coordinate kernel upgrades during maintenance windows to minimize disruption. Additionally, limiting local access to trusted users and enforcing strict access controls can reduce exploitation risk. For environments where immediate patching is not feasible, disabling aRFS or the ice driver temporarily may mitigate the risk, though this could impact network performance. Monitoring kernel logs for BUG reports related to free_irq_cpu_rmap and employing kernel address sanitizer tools in testing environments can help detect attempts to exploit this vulnerability. Finally, organizations should ensure robust incident response plans are in place to quickly address potential exploitation attempts.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2022-49063: Vulnerability in Linux Linux
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2022-49063 is a high-severity use-after-free vulnerability in the Linux kernel affecting the ice network driver, specifically in the handling of IRQ (interrupt request) CPU rmap structures related to the aRFS (accelerated Receive Flow Steering) feature. The vulnerability arises because the function free_irq_cpu_rmap() is called after (devm_)free_irq(), causing it to operate on IRQ descriptors that have already been freed. This improper ordering leads to a use-after-free condition, which is a type of memory corruption where the kernel attempts to access memory that has been released back to the system. The issue was identified through kernel address sanitizer (KASAN) reports triggered by continuous integration testing bots, showing a BUG report with a stack trace pointing to free_irq_cpu_rmap() and related ice driver functions such as ice_remove_arfs and ice_rebuild_arfs. The root cause is that the rmap creation and freeing functions were not symmetrical with the request/free_irq() calls, being performed on device probe/remove/resume instead of on network interface up/down events. This mismatch allows for scenarios, such as device resets, where the rmap is freed prematurely before a new allocation, leading to the use-after-free. The fix involves aligning the lifecycle of the rmap with IRQ request/free calls and ensuring that IRQ affinity notifiers are only cleared when aRFS is disabled, preventing manual interference with CPU rmap sets. The vulnerability impacts Linux kernel versions containing the affected ice driver code, and it has a CVSS 3.1 score of 7.8, indicating high severity with potential for local privilege escalation or denial of service due to corrupted kernel memory. Exploitation requires local privileges but no user interaction, and the vulnerability affects confidentiality, integrity, and availability of the system. No known exploits are reported in the wild as of the publication date.
Potential Impact
For European organizations, this vulnerability poses a significant risk especially to environments running Linux servers with Intel Ethernet controllers using the ice driver, common in data centers, cloud infrastructure, and enterprise networks. Successful exploitation could allow an attacker with local access to cause kernel crashes (denial of service) or potentially escalate privileges by corrupting kernel memory, undermining system integrity and confidentiality. This is particularly critical for sectors relying on high availability and secure data processing such as finance, healthcare, telecommunications, and government institutions. The vulnerability could disrupt critical services and lead to data breaches or system downtime. Given the widespread use of Linux in European IT infrastructure, especially in cloud and virtualization platforms, the impact could be broad if not mitigated promptly.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to versions where this vulnerability is patched. Since the issue is in the ice network driver, organizations should audit their systems to identify usage of Intel Ethernet adapters relying on this driver. Network administrators should coordinate kernel upgrades during maintenance windows to minimize disruption. Additionally, limiting local access to trusted users and enforcing strict access controls can reduce exploitation risk. For environments where immediate patching is not feasible, disabling aRFS or the ice driver temporarily may mitigate the risk, though this could impact network performance. Monitoring kernel logs for BUG reports related to free_irq_cpu_rmap and employing kernel address sanitizer tools in testing environments can help detect attempts to exploit this vulnerability. Finally, organizations should ensure robust incident response plans are in place to quickly address potential exploitation attempts.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-02-26T01:49:39.244Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d982fc4522896dcbe6a3b
Added to database: 5/21/2025, 9:09:03 AM
Last enriched: 7/9/2025, 12:42:17 AM
Last updated: 8/7/2025, 12:54:03 PM
Views: 17
Related Threats
CVE-2025-26398: CWE-798 Use of Hard-coded Credentials in SolarWinds Database Performance Analyzer
MediumCVE-2025-41686: CWE-306 Missing Authentication for Critical Function in Phoenix Contact DaUM
HighCVE-2025-8874: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in litonice13 Master Addons – Elementor Addons with White Label, Free Widgets, Hover Effects, Conditions, & Animations
MediumCVE-2025-8767: CWE-1236 Improper Neutralization of Formula Elements in a CSV File in anwppro AnWP Football Leagues
MediumCVE-2025-8482: CWE-862 Missing Authorization in 10up Simple Local Avatars
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.