CVE-2023-53306
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-01
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.2 (inc) to 6.2.11 (exc) |
| linux | linux_kernel | 6.3 |
| linux | linux_kernel | 6.3 |
| linux | linux_kernel | 6.3 |
| linux | linux_kernel | 6.3 |
| 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 is related to the Linux kernel's handling of CoW (Copy on Write) on non-shared extents in the XFS filesystem. The issue occurs because the old non-shared extent could be marked as dirty due to previous writes, but this dirty mark was not properly cleared before deleting the entry. This leads to a kernel warning and potential instability. The fix involves forcing the clearing of the dirty mark before invalidating inode pages.
How can this vulnerability impact me? :
The vulnerability can cause kernel warnings and potentially lead to instability or crashes in the Linux system when using XFS filesystems with CoW on non-shared extents. This could affect system reliability and data integrity during filesystem operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for the specific WARNING message related to dax_insert_entry in fs/dax.c. You can use the command 'dmesg | grep dax_insert_entry' or 'journalctl -k | grep dax_insert_entry' to check for the warning messages indicating the presence of this issue.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the issue is resolved. The fix involves forcing the clearing of the dirty mark on the dax entry before invalidate_inode_pages2_range(). Until the update is applied, monitoring for the warning messages and avoiding workloads that trigger CoW on non-shared extents in XFS may reduce the risk.