Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50053: iavf: Fix reset error handling

Noroxi assessment

Priority: Monitor (action score 22/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.14% (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 0828e27971f18ea317710acb228afe6e72606082, 31071173771e079f7bc08dacd61e0db913262fbf, 743dc4377bbac06a6fe44c3c5baf75a49439678a.

Low priority for now. Upgrade to Linux Linux 0828e27971f18ea317710acb228afe6e72606082, 31071173771e079f7bc08dacd61e0db913262fbf, 743dc4377bbac06a6fe44c3c5baf75a49439678a 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: iavf: Fix reset error handling Do not call iavf_close in iavf_reset_task error handling. Doing so can lead to double call of napi_disable, which can lead to deadlock there. Removing VF would lead to iavf_remove task being stuck, because it requires crit_lock, which is held by iavf_close. Call iavf_disable_vf if reset fail, so that driver will clean up remaining invalid resources. During rapid VF resets, HW can fail to setup VF mailbox. Wrong error handling can lead to iavf_remove being stuck with: [ 5218.999087] iavf 0000:82:01.0: Failed to init adminq: -53 ... [ 5267.189211] INFO: task repro.sh:11219 blocked for more than 30 seconds. [ 5267.189520] Tainted: G S E 5.18.0-04958-ga54ce3703613-dirty #1 [ 5267.189764] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5267.190062] task:repro.sh state:D stack: 0 pid:11219 ppid: 8162 flags:0x00000000 [ 5267.190347] Call Trace: [ 5267.190647] <TASK> [ 5267.190927] __schedule+0x460/0x9f0 [ 5267.191264] schedule+0x44/0xb0 [ 5267.191563] schedule_preempt_disabled+0x14/0x20 [ 5267.191890] __mutex_lock.isra.12+0x6e3/0xac0 [ 5267.192237] ? iavf_remove+0xf9/0x6c0 [iavf] [ 5267.192565] iavf_remove+0x12a/0x6c0 [iavf] [ 5267.192911] ? _raw_spin_unlock_irqrestore+0x1e/0x40 [ 5267.193285] pci_device_remove+0x36/0xb0 [ 5267.193619] device_release_driver_internal+0xc1/0x150 [ 5267.193974] pci_stop_bus_device+0x69/0x90 [ 5267.194361] pci_stop_and_remove_bus_device+0xe/0x20 [ 5267.194735] pci_iov_remove_virtfn+0xba/0x120 [ 5267.195130] sriov_disable+0x2f/0xe0 [ 5267.195506] ice_free_vfs+0x7d/0x2f0 [ice] [ 5267.196056] ? pci_get_device+0x4f/0x70 [ 5267.196496] ice_sriov_configure+0x78/0x1a0 [ice] [ 5267.196995] sriov_numvfs_store+0xfe/0x140 [ 5267.197466] kernfs_fop_write_iter+0x12e/0x1c0 [ 5267.197918] new_sync_write+0x10c/0x190 [ 5267.198404] vfs_write+0x24e/0x2d0 [ 5267.198886] ksys_write+0x5c/0xd0 [ 5267.199367] do_syscall_64+0x3a/0x80 [ 5267.199827] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 5267.200317] RIP: 0033:0x7f5b381205c8 [ 5267.200814] RSP: 002b:00007fff8c7e8c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 5267.201981] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f5b381205c8 [ 5267.202620] RDX: 0000000000000002 RSI: 00005569420ee900 RDI: 0000000000000001 [ 5267.203426] RBP: 00005569420ee900 R08: 000000000000000a R09: 00007f5b38180820 [ 5267.204327] R10: 000000000000000a R11: 0000000000000246 R12: 00007f5b383c06e0 [ 5267.205193] R13: 0000000000000002 R14: 00007f5b383bb880 R15: 0000000000000002 [ 5267.206041] </TASK> [ 5267.206970] Kernel panic - not syncing: hung_task: blocked tasks [ 5267.207809] CPU: 48 PID: 551 Comm: khungtaskd Kdump: loaded Tainted: G S E 5.18.0-04958-ga54ce3703613-dirty #1 [ 5267.208726] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.11.0 11/02/2019 [ 5267.209623] Call Trace: [ 5267.210569] <TASK> [ 5267.211480] dump_stack_lvl+0x33/0x42 [ 5267.212472] panic+0x107/0x294 [ 5267.213467] watchdog.cold.8+0xc/0xbb [ 5267.214413] ? proc_dohung_task_timeout_secs+0x30/0x30 [ 5267.215511] kthread+0xf4/0x120 [ 5267.216459] ? kthread_complete_and_exit+0x20/0x20 [ 5267.217505] ret_from_fork+0x22/0x30 [ 5267.218459] </TASK>

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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

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 kernel4.14 and later · before 5.15.63
  • linux linux kernel5.16 and later · before 5.19.4
  • 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

    • 4.14affected
    • f0db78928783f0a4cce4940e8c03c2e9a760e629 and later · before 743dc4377bbac06a6fe44c3c5baf75a49439678aaffected · git
    • f0db78928783f0a4cce4940e8c03c2e9a760e629 and later · before 0828e27971f18ea317710acb228afe6e72606082affected · git
    • f0db78928783f0a4cce4940e8c03c2e9a760e629 and later · before 31071173771e079f7bc08dacd61e0db913262fbfaffected · git
    • before 4.14not affected · semver
    • 5.15.63 and later · up to and including 5.15.*not affected · semver
    • 5.19.4 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
Debian:12linuxbefore 5.19.6-15.19.6-1
Red Hat:enterprise_linux:8::baseosbpftoolbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernelbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-corebefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debugbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debug-corebefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debug-develbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debug-modulesbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-docbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-modulesbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-modules-extrabefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-toolsbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-tools-libsbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-zfcpdumpbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-zfcpdump-corebefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-zfcpdump-debuginfobefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-zfcpdump-develbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-zfcpdump-modulesbefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6
Red Hat:enterprise_linux:8::baseoskernel-zfcpdump-modules-extrabefore 0:4.18.0-372.32.1.el8_60:4.18.0-372.32.1.el8_6

+85

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-50051Jun 18, 2025 · ASoC: SOF: debug: Fix potential buffer overflow by snprintf()
    31Monitor
  • ← EarlierCVE-2022-50052Jun 18, 2025 · ASoC: Intel: avs: Fix potential buffer overflow by snprintf()
    31Monitor
  • Later →CVE-2022-50054Jun 18, 2025 · iavf: Fix NULL pointer dereference in iavf_get_link_ksettings
    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 Linux0828e27971f18ea317710acb228afe6e72606082Vendor (CNA)
Linux Linux31071173771e079f7bc08dacd61e0db913262fbfVendor (CNA)
Linux Linux743dc4377bbac06a6fe44c3c5baf75a49439678aVendor (CNA)
debian:linux5.19.6-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-372.32.1.el8_6 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel0:4.18.0-372.32.1.el8_6 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.32.1.el8_6 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-debuginfo0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-debuginfo-common-x86_640:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-devel0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-tools-debuginfo0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:perf0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:perf-debuginfo0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:python3-perf-debuginfo0:4.18.0-372.32.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package 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.

No history yet (it accumulates with the daily EPSS job).

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
none
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
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (2 more)

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

All records