CVE-2023-53172
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.3 |
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 involves the Linux kernel's fsverity feature, where the FS_IOC_ENABLE_VERITY ioctl command was changed to use __kernel_read() instead of direct pagecache accesses. This change made a warning reachable when FS_IOC_ENABLE_VERITY is called on a file descriptor (fd) opened with access mode 3, which means 'ioctl access only'. Since ioctl-only fds are a rare Linux extension and FS_IOC_ENABLE_VERITY requires O_RDONLY mode, the vulnerability is addressed by rejecting the ioctl command on such ioctl-only fds to prevent unexpected behavior.
How can this vulnerability impact me? :
If FS_IOC_ENABLE_VERITY is called on an ioctl-only file descriptor (mode 3), it can trigger a warning in the kernel due to improper access mode handling. While ioctl-only fds are rarely used, this could potentially lead to unexpected kernel warnings or instability when enabling fsverity on such descriptors. The fix prevents this by rejecting the ioctl in these cases, reducing the risk of kernel issues.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is addressed by rejecting the FS_IOC_ENABLE_VERITY ioctl on file descriptors opened with access mode 3 (ioctl-only). To mitigate this vulnerability, ensure that FS_IOC_ENABLE_VERITY is not called on ioctl-only file descriptors and that file descriptors used with this ioctl are opened with O_RDONLY mode as documented. Applying the kernel update that includes the fix (commit 56124d6c87fd) will also mitigate the issue.