NULL Pointer Dereference Affecting kernel-zfcpdump-devel-matched package, versions <0:6.12.0-211.51.1.el10_2


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.16% (5th 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-ROCKY10-KERNELZFCPDUMPDEVELMATCHED-19634742
  • published6 Sept 2026
  • disclosed24 Jun 2026

Introduced: 24 Jun 2026

CVE-2026-53073  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:10 kernel-zfcpdump-devel-matched to version 0:6.12.0-211.51.1.el10_2 or higher.
This issue was patched in RLSA-2026:63128.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump-devel-matched package and not the kernel-zfcpdump-devel-matched package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:10 relevant fixed versions and status.

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

Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error

When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu->proto->close(hu) and setting hu->hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed.

Clear HCI_UART_PROTO_INIT with a write lock before calling hu->proto->close() and setting hu->hdev to NULL. The write lock ensures all active readers have completed and no new reader can enter the protocol recv path before resources are freed.

This allows the protocol-specific recv functions to remove the "HCI_UART_REGISTERED" guard without risking a null pointer dereference if hci_register_dev() fails.

CVSS Base Scores

version 3.1