Description
In the Linux kernel, the following vulnerability has been resolved: dlm: fix possible lkb_resource null dereference This patch fixes a possible null pointer dereference when this function is called from request_lock() as lkb->lkb_resource is not assigned yet, only after validate_lock_args() by calling attach_lkb(). Another issue is that a resource name could be a non printable bytearray and we cannot assume to be ASCII coded. The log functionality is probably never being hit when DLM is used in normal way and no debug logging is enabled. The null pointer dereference can only occur on a new created lkb that does not have the resource assigned yet, it probably never hits the null pointer dereference but we should be sure that other changes might not change this behaviour and we actually can hit the mentioned null pointer dereference. In this patch we just drop the printout of the resource name, the lkb id is enough to make a possible connection to a resource name if this exists.
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 6.8.0-58.60 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 6.8.0-1027.29 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | — |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | — |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-6.8 | — | 6.8.0-1027.29~22.04.1 |
| linux-aws-fips | — | — |
| linux-aws-hwe | — | — |
| linux-azure | — | 6.8.0-1027.32 |
| linux-azure-4.15 | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | — |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | — |
| linux-azure-5.8 | — | — |
| linux-azure-6.11 | — | 6.11.0-1012.12~24.04.1 |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-6.8 | — | 6.8.0-1027.32~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.15 | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | — |
| linux-azure-nvidia | — | 6.8.0-1014.15 |
| linux-bluefield | — | — |
| linux-fips | — | 6.8.0-78.78+fips1 |
| linux-gcp | — | 6.8.0-1028.30 |
| linux-gcp-4.15 | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | — |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | — |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.11 | — | 6.11.0-1011.11~24.04.1 |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-6.8 | — | 6.8.0-1028.30~22.04.1 |
| linux-gcp-fips | — | — |
| linux-gke | — | 6.8.0-1023.27 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 6.8.0-1010.12 |
| linux-gkeop-5.15 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | — |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | — |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.11 | — | 6.11.0-21.21~24.04.1 |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-6.8 | — | 6.8.0-58.60~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 6.8.0-1024.24 |
| linux-ibm-5.15 | — | — |
| linux-ibm-5.4 | — | — |
| linux-ibm-6.8 | — | 6.8.0-1024.24~22.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | — |
| linux-intel-iotg | — | — |
| linux-intel-iotg-5.15 | — | — |
| linux-iot | — | — |
| linux-kvm | — | — |
| linux-lowlatency | — | 6.8.0-58.60.1 |
| linux-lowlatency-hwe-5.15 | — | — |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-lowlatency-hwe-6.8 | — | 6.8.0-58.60.1~22.04.1 |
| linux-lts-xenial | — | — |
| linux-nvidia | — | 6.8.0-1026.29 |
| linux-nvidia-6.11 | — | 6.11.0-1007.7 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-6.8 | — | 6.8.0-1026.29~22.04.1 |
| linux-nvidia-lowlatency | — | 6.8.0-1026.29.1 |
| linux-nvidia-tegra | — | 6.8.0-1008.8 |
| linux-nvidia-tegra-5.15 | — | — |
| linux-nvidia-tegra-igx | — | — |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | 6.11.0-1017.17 |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | 6.8.0-1026.26 |
| linux-oracle | — | 6.8.0-1024.25 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | — |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | — |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-oracle-6.8 | — | 6.8.0-1024.25~22.04.1 |
| linux-raspi | — | 6.8.0-1028.32 |
| linux-raspi-5.4 | — | — |
| linux-raspi-realtime | — | 6.8.0-2023.24 |
| linux-raspi2 | — | — |
| linux-realtime | — | 6.8.1-1020.21 |
| linux-realtime-6.8 | — | 6.8.1-1020.21~22.04.1 |
| linux-riscv | — | 6.8.0-58.60.1 |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | — |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-riscv-6.8 | — | 6.8.0-58.60.1~22.04.1 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx | — | 6.8.0-1017.18 |
| linux-xilinx-zynqmp | — | — |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Exploit Protection
Help block exploit attempts
BotEraser is designed to detect and help reduce malicious bot traffic that may target known vulnerabilities on your site.
Try BotEraser Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
