CVE-2022-50055

iavf: Fix adminq error handling

MEDIUM

5.5

CVSS Score

Published: June 18, 2025 at 11:01 AM UTC

Updated: June 17, 2026 at 05:22 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: iavf: Fix adminq error handling iavf_alloc_asq_bufs/iavf_alloc_arq_bufs allocates with dma_alloc_coherent memory for VF mailbox. Free DMA regions for both ASQ and ARQ in case error happens during configuration of ASQ/ARQ registers. Without this change it is possible to see when unloading interface: 74626.583369: dma_debug_device_change: device driver has pending DMA allocations while released from device [count=32] One of leaked entries details: [device address=0x0000000b27ff9000] [size=4096 bytes] [mapped with DMA_BIDIRECTIONAL] [mapped as coherent]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.14 ≤ v < 5.10.1383.14 ≤ v < 5.15.633.14 ≤ v < 5.19.43.14 ≤ v < 5.4.2113.14 ≤ v < 6.05.11 ≤ v < 5.15.635.16 ≤ v < 5.19.45.5 ≤ v < 5.10.1383.14 6.0 rc1d358aa9a7a2d5f91b1d33d5d4e27c2e46638d123

Vendor states this is fixed in 35c63581fdefdcbaeae8cded18908523252353ad (fixed)

Vendor states this is fixed in 419831617ed349992c84344dbd9e627f9e68f842 (fixed)

Vendor states this is fixed in 4fe80492d53971d9a49f39f3c86d2d67c6f3638a (fixed)

Vendor states this is fixed in dab6b551f5ba4c79a0dd4970dd8533c37a7b100f (fixed)

Vendor states this is fixed in ff289f2be5899efd0e897d2b434a78e36df2c69b (fixed)

Vendor states this is fixed in 3.14 (unaffected)

Vendor states this is fixed in 5.10.138 (unaffected)

Vendor states this is fixed in 5.15.63 (unaffected)

Vendor states this is fixed in 5.19.4 (unaffected)

Vendor states this is fixed in 5.4.211 (unaffected)

Vendor states this is fixed in 6.0 (unaffected)