CVE-2023-53217
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.18 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.120 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.38 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.12 (exc) |
| linux | linux_kernel | From 6.4 (inc) to 6.4.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a regression in the Linux kernel related to the nubus subsystem. A change converting code to use proc_create_single_data() caused a segmentation fault when reading files in /proc/bus/nubus. The issue arises because the new code using single_open(file, nubus_proc_rsrc_show, PDE_DATA(inode)) is not equivalent to the original implementation, leading to a kernel crash (segmentation fault) when accessing certain proc files.
How can this vulnerability impact me? :
This vulnerability can cause a kernel crash (segmentation fault) when reading files in /proc/bus/nubus, potentially leading to system instability or denial of service. Users or processes attempting to access these proc files may cause the kernel to fault, which could disrupt normal system operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to read files under /proc/bus/nubus and observing if a segmentation fault or kernel oops occurs. For example, running the command `grep -r . /proc/bus/nubus/e/` may trigger the fault and produce kernel error messages similar to those described in the vulnerability details.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves avoiding reading files in /proc/bus/nubus until the kernel is patched. Applying the kernel update that reverts the proc_create_single_data() conversion for nubus is necessary to resolve the issue.