Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49954: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag

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 98e01215708b6d416345465c09dce2bd4868c67a, b271090eea3899399e2adcf79c9c95367d472b03, b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c.

Low priority for now. Upgrade to Linux Linux 98e01215708b6d416345465c09dce2bd4868c67a, b271090eea3899399e2adcf79c9c95367d472b03, b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c 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: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev->mutex held is blocking input_disconnect_device() from __input_unregister_device(). It seems that the cause is simply that commit c2b27ef672992a20 ("Input: iforce - wait for command completion when closing the device") forgot to call wake_up() after clear_bit(). Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().

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

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 kernel2.6.34 and later · before 5.4.213
  • linux linux kernel5.5 and later · before 5.10.142
  • linux linux kernel5.11 and later · before 5.15.66
  • linux linux kernel5.16 and later · before 5.19.8
  • linux linux kernel2.6.33
  • 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

    • 2.6.33affected
    • c2b27ef672992a206e5b221b8676972dd840ffa5 and later · before d186c65599bff0222da37b9215784ddfe39f9e1baffected · git
    • c2b27ef672992a206e5b221b8676972dd840ffa5 and later · before b271090eea3899399e2adcf79c9c95367d472b03affected · git
    • c2b27ef672992a206e5b221b8676972dd840ffa5 and later · before df1b53bc799d58f79701c465505a206c72ad4ab8affected · git
    • c2b27ef672992a206e5b221b8676972dd840ffa5 and later · before b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3caffected · git
    • c2b27ef672992a206e5b221b8676972dd840ffa5 and later · before 98e01215708b6d416345465c09dce2bd4868c67aaffected · git
    • before 2.6.33not affected · semver
    • 5.4.213 and later · up to and including 5.4.*not affected · semver
    • 5.10.142 and later · up to and including 5.10.*not affected · semver
    • 5.15.66 and later · up to and including 5.15.*not 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
SUSE:Linux Enterprise Live Patching 15 SP3kernel-defaultbefore 5.3.18-150300.59.211.15.3.18-150300.59.211.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-livepatch-SLE15-SP3_Update_59before 1-150300.7.3.11-150300.7.3.1
SUSE:Linux Enterprise Micro 5.1kernel-rtbefore 5.3.18-150300.214.15.3.18-150300.214.1
SUSE:Linux Enterprise Micro 5.1kernel-source-rtbefore 5.3.18-150300.214.15.3.18-150300.214.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-64kbbefore 5.3.18-150300.59.211.15.3.18-150300.59.211.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-default-basebefore 5.3.18-150300.59.211.1.150300.18.126.15.3.18-150300.59.211.1.150300.18.126.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-docsbefore 5.3.18-150300.59.211.15.3.18-150300.59.211.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-obs-buildbefore 5.3.18-150300.59.212.15.3.18-150300.59.212.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-preemptbefore 5.3.18-150300.59.211.15.3.18-150300.59.211.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-sourcebefore 5.3.18-150300.59.211.15.3.18-150300.59.211.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-symsbefore 5.3.18-150300.59.211.15.3.18-150300.59.211.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-zfcpdumpbefore 5.3.18-150300.59.211.15.3.18-150300.59.211.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-49952Jun 18, 2025 · misc: fastrpc: fix memory corruption on probe
    31Monitor
  • ← EarlierCVE-2022-49953Jun 18, 2025 · iio: light: cm3605: Fix an error handling path in cm3605_probe()
    22Monitor
  • Later →CVE-2022-49956Jun 18, 2025 · staging: rtl8712: fix use after free bugs
    31Monitor

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 Linux98e01215708b6d416345465c09dce2bd4868c67aVendor (CNA)
Linux Linuxb271090eea3899399e2adcf79c9c95367d472b03Vendor (CNA)
Linux Linuxb533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3cVendor (CNA)
Linux Linuxd186c65599bff0222da37b9215784ddfe39f9e1bVendor (CNA)
Linux Linuxdf1b53bc799d58f79701c465505a206c72ad4ab8Vendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.211.1.150300.18.126.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_591-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.212.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-rt5.3.18-150300.214.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-source5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-source-rt5.3.18-150300.214.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-syms5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-zfcpdump5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage 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 (4 more)

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

All records