UFS startup fault via uninitialized SCSI tag set
Published Dec 16, 2025 · Updated Dec 16, 2025
The Linux Kernel SCSI core received this identifier for a scsi_host_busy() initialization regression during UFS driver probing. The function called blk_mq_tagset_busy_iter() before the host tag set ops field had been initialized, producing an SRCU lock trace during startup. Kernel.org later rejected the CVE and removed every affected-version reference, so the identifier no longer represents a confirmed vulnerability.
Summary
What happened
The Linux Kernel SCSI core received this identifier for a scsi_host_busy() initialization regression during UFS driver probing. The function called blk_mq_tagset_busy_iter() before the host tag set ops field had been initialized, producing an SRCU lock trace during startup. Kernel.org later rejected the CVE and removed every affected-version reference, so the identifier no longer represents a confirmed vulnerability.
The record
- CVE
- CVE-2025-68224
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 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 <143257917b836bd5fc434063030fda199e249624
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47c8b35a1f1d53aac156480cea0a0c5c82919f03
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d778778b40bcdfd9f8817fea1ec6ebcbec69c0a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <804b5b8e3545445450387ae6891262c421c49304
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a0b7780602b1b196f47e527fec82166a7e67c4d0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d579f496681c5136d63cb4fbb685511227e73602
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e208fb1660c4a43f06b7b66c3ff22dde84ec3990
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
No public exploit references are available in this record.
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