Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49434: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()

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.21% (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 2cdd5284035322795b0964f899eefba254cfe483, 59ea6b3ae51df7cd6bfd84c9c0030609b9315622, a91ee0e9fca9d7501286cfbced9b30a33e52740a.

Low priority for now. Upgrade to Linux Linux 2cdd5284035322795b0964f899eefba254cfe483, 59ea6b3ae51df7cd6bfd84c9c0030609b9315622, a91ee0e9fca9d7501286cfbced9b30a33e52740a 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: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock: sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev->block_cfg_access == 0 Previously, pci_dev_lock() acquired the config space access lock before the device lock: pci_dev_lock pci_cfg_access_lock dev->block_cfg_access = 1 # B (2) set dev->block_cfg_access = 1 device_lock # A (3) wait for device lock Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4). Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path. [bhelgaas: combined and adapted commit log from Jay Zhou's independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th 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.2%

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

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 kernelbefore 4.9.318
  • linux linux kernel4.10 and later · before 4.14.283
  • linux linux kernel4.15 and later · before 4.19.247
  • linux linux kernel4.20 and later · before 5.4.198
  • linux linux kernel5.5 and later · before 5.10.121
  • linux linux kernel5.11 and later · before 5.15.46
  • linux linux kernel5.16 and later · before 5.17.14
  • linux linux kernel5.18 and later · before 5.18.3

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.13affected
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before c3c6dc1853b8bf3c718f96fd8480a6eb09ba4831affected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before aed6d4d519210c28817948f34c53b6e058e0456caffected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before c9a81f9ed6ae3554621d6a50220b1bc74b67d81eaffected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before eff3587b9c01439b738298475e555c028ac9f55eaffected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before 2cdd5284035322795b0964f899eefba254cfe483affected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before ea047f51172aa68841adef7f52d375002438b8f0affected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before 59ea6b3ae51df7cd6bfd84c9c0030609b9315622affected · git
    • 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e and later · before a91ee0e9fca9d7501286cfbced9b30a33e52740aaffected · git
    • before 4.13not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.5-15.18.5-1

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-49432Feb 26, 2025 · powerpc/xics: fix refcount leak in icp_opal_init()
    22Monitor
  • ← EarlierCVE-2022-49433Feb 26, 2025 · RDMA/hfi1: Prevent use of lock before it is initialized
    22Monitor
  • Later →CVE-2022-49435Feb 26, 2025 · mfd: davinci_voicecodec: Fix possible null-ptr-deref davinci_vc_probe()
    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 Linux2cdd5284035322795b0964f899eefba254cfe483Vendor (CNA)
Linux Linux59ea6b3ae51df7cd6bfd84c9c0030609b9315622Vendor (CNA)
Linux Linuxa91ee0e9fca9d7501286cfbced9b30a33e52740aVendor (CNA)
Linux Linuxaed6d4d519210c28817948f34c53b6e058e0456cVendor (CNA)
Linux Linuxc3c6dc1853b8bf3c718f96fd8480a6eb09ba4831Vendor (CNA)
Linux Linuxc9a81f9ed6ae3554621d6a50220b1bc74b67d81eVendor (CNA)
Linux Linuxea047f51172aa68841adef7f52d375002438b8f0Vendor (CNA)
Linux Linuxeff3587b9c01439b738298475e555c028ac9f55eVendor (CNA)
debian:linux5.18.5-1 · Debian:12Package 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
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 (7 more)

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

All records