NULL Pointer Dereference Affecting kernel-64k-debug-devel-matched package, versions <0:5.14.0-427.13.1.el9_4


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.19% (9th 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-RHEL9-KERNEL64KDEBUGDEVELMATCHED-13180907
  • published2 Oct 2025
  • disclosed17 Sept 2025

Introduced: 17 Sep 2025

CVE-2022-50374  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade RHEL:9 kernel-64k-debug-devel-matched to version 0:5.14.0-427.13.1.el9_4 or higher.
This issue was patched in RHSA-2024:2394.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-64k-debug-devel-matched package and not the kernel-64k-debug-devel-matched package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure

syzbot is reporting NULL pointer dereference at hci_uart_tty_close() [1], for rcu_sync_enter() is called without rcu_sync_init() due to hci_uart_tty_open() ignoring percpu_init_rwsem() failure.

While we are at it, fix that hci_uart_register_device() ignores percpu_init_rwsem() failure and hci_uart_unregister_device() does not call percpu_free_rwsem().

CVSS Base Scores

version 3.1