Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50202: PM: hibernate: defer device probing when resuming from hibernation

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.25% (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 003a456ae6f70bb97e436e02fc5105be577c1570, 2f0e18e0db42f4f8bc87d3d98333680065ceeff8, 3c48d3067eaf878642276f053575a5c642600a50.

Low priority for now. Upgrade to Linux Linux 003a456ae6f70bb97e436e02fc5105be577c1570, 2f0e18e0db42f4f8bc87d3d98333680065ceeff8, 3c48d3067eaf878642276f053575a5c642600a50 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: PM: hibernate: defer device probing when resuming from hibernation syzbot is reporting hung task at misc_open() [1], for there is a race window of AB-BA deadlock which involves probe_count variable. Currently wait_for_device_probe() from snapshot_open() from misc_open() can sleep forever with misc_mtx held if probe_count cannot become 0. When a device is probed by hub_event() work function, probe_count is incremented before the probe function starts, and probe_count is decremented after the probe function completed. There are three cases that can prevent probe_count from dropping to 0. (a) A device being probed stopped responding (i.e. broken/malicious hardware). (b) A process emulating a USB device using /dev/raw-gadget interface stopped responding for some reason. (c) New device probe requests keeps coming in before existing device probe requests complete. The phenomenon syzbot is reporting is (b). A process which is holding system_transition_mutex and misc_mtx is waiting for probe_count to become 0 inside wait_for_device_probe(), but the probe function which is called from hub_event() work function is waiting for the processes which are blocked at mutex_lock(&misc_mtx) to respond via /dev/raw-gadget interface. This patch mitigates (b) by deferring wait_for_device_probe() from snapshot_open() to snapshot_write() and snapshot_ioctl(). Please note that the possibility of (b) remains as long as any thread which is emulating a USB device via /dev/raw-gadget interface can be blocked by uninterruptible blocking operations (e.g. mutex_lock()). Please also note that (a) and (c) are not addressed. Regarding (c), we should change the code to wait for only one device which contains the image for resuming from hibernation. I don't know how to address (a), for use of timeout for wait_for_device_probe() might result in loss of user data in the image. Maybe we should require the userland to wait for the image device before opening /dev/snapshot interface.

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

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

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.14.291
  • linux linux kernel4.15 and later · before 4.19.256
  • linux linux kernel4.20 and later · before 5.4.211
  • linux linux kernel5.5 and later · before 5.10.137
  • linux linux kernel5.11 and later · before 5.15.61
  • linux linux kernel5.16 and later · before 5.18.18
  • linux linux kernel5.19 and later · before 5.19.2

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

    • 2.6.30affected
    • c751085943362143f84346d274e0011419c84202 and later · before 8c90947e5f1801e6c7120021c6ea0f3ad6a4eb91affected · git
    • c751085943362143f84346d274e0011419c84202 and later · before 5a283b59bce72c05c60e9f0fa92a28b5b850d8bbaffected · git
    • c751085943362143f84346d274e0011419c84202 and later · before 3c48d3067eaf878642276f053575a5c642600a50affected · git
    • c751085943362143f84346d274e0011419c84202 and later · before 003a456ae6f70bb97e436e02fc5105be577c1570affected · git
    • c751085943362143f84346d274e0011419c84202 and later · before 2f0e18e0db42f4f8bc87d3d98333680065ceeff8affected · git
    • c751085943362143f84346d274e0011419c84202 and later · before b8e1ae9433d7bd95f2dcc044a7a6f20a4c40d258affected · git
    • c751085943362143f84346d274e0011419c84202 and later · before f7042cf9dd40733f387b7cac021e626c74b8856faffected · git
    • c751085943362143f84346d274e0011419c84202 and later · before 8386c414e27caba8501119948e9551e52b527f59affected · git
    • before 2.6.30not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.2-16.0.2-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:7.3.0-427.13.1.el9_40:7.3.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4

+55

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-50199Jun 18, 2025 · ARM: OMAP2+: Fix refcount leak in omapdss_init_of
    22Monitor
  • ← EarlierCVE-2022-50201Jun 18, 2025 · selinux: fix memleak in security_read_state_kernel()
    22Monitor
  • Later →CVE-2022-50203Jun 18, 2025 · ARM: OMAP2+: display: Fix refcount leak bug
    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 Linux003a456ae6f70bb97e436e02fc5105be577c1570Vendor (CNA)
Linux Linux2f0e18e0db42f4f8bc87d3d98333680065ceeff8Vendor (CNA)
Linux Linux3c48d3067eaf878642276f053575a5c642600a50Vendor (CNA)
Linux Linux5a283b59bce72c05c60e9f0fa92a28b5b850d8bbVendor (CNA)
Linux Linux8386c414e27caba8501119948e9551e52b527f59Vendor (CNA)
Linux Linux8c90947e5f1801e6c7120021c6ea0f3ad6a4eb91Vendor (CNA)
Linux Linuxb8e1ae9433d7bd95f2dcc044a7a6f20a4c40d258Vendor (CNA)
Linux Linuxf7042cf9dd40733f387b7cac021e626c74b8856fVendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.13.1.el9_4 · 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.

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)

—

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.

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

Show all references (7 more)

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

All records