Service interruption via unlocked loop-device resizing
Published Sep 4, 2025 · Updated May 11, 2026
Improper locking in affected Linux kernel revisions allows local users to interrupt service by resizing a mounted loop device. The loop_set_block_size function changes the device's logical block size without first obtaining exclusive ownership, leaving it inconsistent with the mounted filesystem's superblock. Access to issue LOOP_SET_BLOCK_SIZE against a loop device held by a mounted filesystem is required; the demonstrated result is a kernel warning and inconsistent buffer accounting.
Summary
What happened
Improper locking in affected Linux kernel revisions allows local users to interrupt service by resizing a mounted loop device. The loop_set_block_size function changes the device's logical block size without first obtaining exclusive ownership, leaving it inconsistent with the mounted filesystem's superblock. Access to issue LOOP_SET_BLOCK_SIZE against a loop device held by a mounted filesystem is required; the demonstrated result is a kernel warning and inconsistent buffer accounting.
The record
- CVE
- CVE-2025-38709
- Published
- Sep 4, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=4.14
- Affected versionversion=89e4fdecb51cf5535867026274bc97de9480ade5 <139a000d20f2f38ce34296feddd641d730fe1c08
- Affected versionversion=89e4fdecb51cf5535867026274bc97de9480ade5 <457d2c5e112fd08dc1039b1ae39a83ec1782360d
- Affected versionversion=89e4fdecb51cf5535867026274bc97de9480ade5 <5d67b30aefeb7a949040bbb1b4e3b84c5d29a624
- Affected versionversion=89e4fdecb51cf5535867026274bc97de9480ade5 <7e49538288e523427beedd26993d446afef1a6fb
- Affected versionversion=89e4fdecb51cf5535867026274bc97de9480ade5 <b928438cc87c0bf7ae078e4b7b6e14261e84c5c5
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
Public exploit references
- syzkaller loop-device block-size reproducerproof 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