CVE-2022-49954 Affecting kernel-livepatch-5_14_21-150400_24_170-default package, versions <1-150400.9.3.2


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.03% (7th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES154-KERNELLIVEPATCH5142115040024170DEFAULT-11175027
  • published29 Jul 2025
  • disclosed28 Jul 2025

Introduced: 28 Jul 2025

CVE-2022-49954  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 kernel-livepatch-5_14_21-150400_24_170-default to version 1-150400.9.3.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-5_14_21-150400_24_170-default package and not the kernel-livepatch-5_14_21-150400_24_170-default package as distributed by SLES. See How to fix? for SLES:15.4 relevant fixed versions and status.

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().

CVSS Base Scores

version 3.1