Kernel crash via unchecked sb_getblk failure
Published Dec 30, 2025 · Updated Dec 30, 2025
NULL-pointer dereference in Linux kernel SysV filesystems allows attackers to crash affected systems during block allocation. In alloc_branch(), sb_getblk() can return NULL, but the code passes that pointer to lock_buffer() without checking the allocation result. The failure path requires a SysV inode branch allocation and an sb_getblk() failure; published sources do not establish the privileges needed to reach it.
Summary
What happened
NULL-pointer dereference in Linux kernel SysV filesystems allows attackers to crash affected systems during block allocation. In alloc_branch(), sb_getblk() can return NULL, but the code passes that pointer to lock_buffer() without checking the allocation result. The failure path requires a SysV inode branch allocation and an sb_getblk() failure; published sources do not establish the privileges needed to reach it.
The record
- CVE
- CVE-2023-54264
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0a44ceba77c3267f8505dda102a59367dc24caee
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1416eebaad80bdc85ad9f97f27242011b031e2a9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f740bc696d4617f8ee44565e8ac0d36278a1e91
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <afd9a31b5aa4b3747f382d44a7b03b7b5d0b7635
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <baa60c66a310c50785289b0ede6fdce8ec3219c7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e28f376dd8dfcc4e880ac101184132bc08703f6e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e976988bc245ec3768cc0f76bed7d05488a7dd0f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ea2b62f305893992156a798f665847e0663c9f41
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- syzbot C reproducer for NULL dereference in get_blockproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo