Kernel warning via uninitialized NAND operation
Published May 9, 2025 · Updated May 11, 2026
Use of an uninitialized resource in Linux's Broadcom raw NAND driver allows local users to trigger a kernel warning during PM resume. The brcmnand_resume path calls nand_reset_op with an uninitialized nand_operation, so its chip-select check reads an indeterminate cs field. Reaching the path requires CAP_SYS_ADMIN in the initial user namespace and compatible single-die Broadcom STB NAND hardware; the public record demonstrates a warning and kernel taint, not a crash or data corruption.
Summary
What happened
Use of an uninitialized resource in Linux's Broadcom raw NAND driver allows local users to trigger a kernel warning during PM resume. The brcmnand_resume path calls nand_reset_op with an uninitialized nand_operation, so its chip-select check reads an indeterminate cs field. Reaching the path requires CAP_SYS_ADMIN in the initial user namespace and compatible single-die Broadcom STB NAND hardware; the public record demonstrates a warning and kernel taint, not a crash or data corruption.
The record
- CVE
- CVE-2025-37840
- Published
- May 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 9, 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.16
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <659b1f29f3e2fd5d751fdf35c5526d1f1c9b3dd2
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <6f567c6a5250e3531cfd9c7ff254ecc2650464fa
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <7266066b9469f04ed1d4c0fdddaea1425835eb55
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <8775581e1c48e1bdd04a893d6f6bbe5128ad0ea7
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <9bd51723ab51580e077c91d494c37e80703b8524
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <9dd161f707ecb7db38e5f529e979a5b6eb565b2d
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <c2eb3cffb0d972c5503e4d48921971c81def0fe5
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <ddc210cf8b8a8be68051ad958bf3e2cef6b681c2
- Affected versionversion=97d90da8a886949f09bb4754843fb0b504956ad2 <fbcb584efa5cd912ff8a151d67b8fe22f4162a85
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
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