Kernel warning via incorrect RAID discard limits
Published Dec 8, 2025 · Updated May 11, 2026
Incorrect discard limits in Linux kernel 5.19 through 6.0.15 and 6.1 through 6.1.1 allow local users to trigger a kernel warning. The md RAID0 and RAID10 queue setup writes max_discard_sectors directly when every member is rotational instead of deriving stacked limits with disk_stack_limits. The trigger requires access to an affected md array and permission to create an XFS filesystem; the public record demonstrates a warning in __blkdev_issue_discard but no crash or data loss.
Summary
What happened
Incorrect discard limits in Linux kernel 5.19 through 6.0.15 and 6.1 through 6.1.1 allow local users to trigger a kernel warning. The md RAID0 and RAID10 queue setup writes max_discard_sectors directly when every member is rotational instead of deriving stacked limits with disk_stack_limits. The trigger requires access to an affected md array and permission to create an XFS filesystem; the public record demonstrates a warning in __blkdev_issue_discard but no crash or data loss.
The record
- CVE
- CVE-2022-50583
- Published
- Dec 8, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 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=5.19
- Affected versionversion=70200574cc229f6ba038259e8142af2aa09e6976 <27e5d61a8e6919b5c0c6f473703ffea2acba862a
- Affected versionversion=70200574cc229f6ba038259e8142af2aa09e6976 <8e1a2279ca2b0485cc379a153d02a9793f74a48f
- Affected versionversion=70200574cc229f6ba038259e8142af2aa09e6976 <e80bef070699d2e791badefccb1ddabd6998d468
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