Vulnerability · CVE-2023-54281
In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before inode lookup during the ino lookup ioctl During the ino lookup ioctl we can end up ca
Published Dec 30, 2025 · catalog updated May 11, 2026 · Linux Linux
Last checked Nov 1, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2023-54281. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-99270 · High
- CVE-2026-99269 · High
- CVE-2026-99267 · Unknown
- CVE-2026-99266 · Unknown
- CVE-2026-99265 · Unknown
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.20%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 23d0b79dfaed2305b500b0215b0421701ada6b1a <7390bb377b5fb3be23cb021e0f184d1f576be7d6
In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before inode lookup during the ino lookup ioctl During the ino lookup ioctl we can end up calling btrfs_iget() to get an inode reference while we are holding on a root's btree. If btrfs_iget() needs to lookup the inode from the root's btree, because it's not currently loaded in memory, then it will need to lock another or the same path in the same root btree. This may result in a deadlock and trigger the following lockdep splat: WARNING: possible circular locking dependency detected 6.5.0-rc7-syzkaller-0000
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 23d0b79dfaed2305b500b0215b0421701ada6b1a <7390bb377b5fb3be23cb021e0f184d1f576be7d623d0b79dfaed2305b500b0215b0421701ada6b1a <7390bb377b5fb3be23cb021e0f184d1f576be7d6
How to fix CVE-2023-54281
Upgrade
CVE-2023-54281 lists a fix boundary at 7390bb377b5fb3be23cb021e0f184d1f576be7d6. Compare the installed build with that boundary before you change production.
Version check
Seen in 23d0b79dfaed2305b500b0215b0421701ada6b1a <7390bb377b5fb3be23cb021e0f184d1f576be7d6
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2023-54281. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Linux Linux 23d0b79dfaed2305b500b0215b0421701ada6b1a <7390bb377b5fb3be23cb021e0f184d1f576be7d6 23d0b79dfaed2305b500b0215b0421701ada6b1a <7390bb377b5fb3be23cb021e0f184d1f576be7d6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Dec 30, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before inode lookup during the ino lookup ioctl During the ino lookup ioctl we can end up calling btrfs_iget() to get an inode reference while we are holding on a root's btree. If btrfs_iget() needs to lookup the inode from the root's btree, because it's not currently loaded in memory, then it will need to lock
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before inode lookup during the ino lookup ioctl During the ino lookup ioctl we can end up calling btrfs_iget() to get an inode reference while we are holding on a root's btree. If btrfs_iget() needs to lookup the inode from the root's btree, because it's not currently loaded in memory, then it will need to lock
Sources
- CVE.orgVulnerability recordCVE-2023-54281
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-54281
30-day exploitation probability 0.20%
first.org - EUVDVulnerability recordEUVD-2023-60523
In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before inode lookup during the ino lookup ioctl During the ino lookup ioctl we can end up calling btrfs_iget() to get an inode reference while we are holding on a root's btree. If btrfs_iget()
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 1, 2026
- CVE.orgOct 29, 2026
- EUVDOct 29, 2026