CVE-2023-52810·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add check for negative db_l2nbperpage l2nbperpage is log2(number of blks per page), and the minimum legal value should be 0, not negative. In the case of l2nbperpage being negative, an error will occur when subsequently used as shift exponent. Syzbot reported this bug: UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:799:12 shift exponent -16777216 is negative
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.6.3
- Published
- 2024-05-21
Affected versions
From: 6.6
Until: 6.6.3
Fixed in: 6.6.3
How to fix this CVE
Update your Linux kernel to version 6.6.3 or later to patch the JFS filesystem validation flaw that permits negative shift exponent values. Systems running kernels 6.6 through 6.6.2 should prioritize this update to prevent potential kernel panics or out-of-bounds shifts during JFS operations. Apply the patch through your distribution's standard kernel update mechanism.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your current kernel version: uname -r (look for versions 6.6.0 through 6.6.2)
- Verify if JFS is active: grep -i jfs /proc/filesystems or mount | grep jfs
- Monitor kernel logs for shift-out-of-bounds errors: dmesg | grep -i 'shift\|jfs_dmap'
- Confirm the patch is applied by checking kernel build info: cat /proc/version | grep 6.6.3 or later
FAQ
What is CVE-2023-52810?
CVE-2023-52810 is a kernel validation flaw in the JFS (Journaled File System) driver where a negative db_l2nbperpage value can trigger an invalid shift operation, causing kernel panics or undefined behavior. The vulnerability exists because insufficient input validation allows negative logarithmic block-per-page values to reach bit-shift operations.
Is CVE-2023-52810 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, it can be triggered via malformed JFS filesystem metadata, making local exploitation possible.
What versions of Kernel are affected by CVE-2023-52810?
Linux kernel versions 6.6.0, 6.6.1, and 6.6.2 are affected. Version 6.6.3 and later contain the fix.
How do I check if my server is vulnerable to CVE-2023-52810?
Run `uname -r` and check if the output matches 6.6.0 through 6.6.2, then verify JFS is mounted with `mount | grep jfs`. If both conditions are true, your system is vulnerable.
Does Defensia detect CVE-2023-52810?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Linux kernel is installed on a monitored server, CVE-2023-52810 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0cb567e727339a192f9fd0db00781d73a91d15a6
- https://git.kernel.org/stable/c/1a7c53fdea1d189087544d9a606d249e93c4934b
- https://git.kernel.org/stable/c/491085258185ffc4fb91555b0dba895fe7656a45
- https://git.kernel.org/stable/c/524b4f203afcf87accfe387e846f33f916f0c907
- https://git.kernel.org/stable/c/525b861a008143048535011f3816d407940f4bfa
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2023-52810. Free for 1 server.
Get started free