CVE-2022-50583
Description
In the Linux kernel, the following vulnerability has been resolved:
md/raid0, raid10: Don't set discard sectors for request queue
It should use disk_stack_limits to get a proper max_discard_sectors rather than setting a value by stack drivers.
And there is a bug. If all member disks are rotational devices, raid0/raid10 set max_discard_sectors. So the member devices are not ssd/nvme, but raid0/raid10 export the wrong value. It reports warning messages in function __blkdev_issue_discard when mkfs.xfs like this:
[ 4616.022599] ------------[ cut here ]------------ [ 4616.027779] WARNING: CPU: 4 PID: 99634 at block/blk-lib.c:50 __blkdev_issue_discard+0x16a/0x1a0 [ 4616.140663] RIP: 0010:__blkdev_issue_discard+0x16a/0x1a0 [ 4616.146601] Code: 24 4c 89 20 31 c0 e9 fe fe ff ff c1 e8 09 8d 48 ff 4c 89 f0 4c 09 e8 48 85 c1 0f 84 55 ff ff ff b8 ea ff ff ff e9 df fe ff ff <0f> 0b 48 8d 74 24 08 e8 ea d6 00 00 48 c7 c6 20 1e 89 ab 48 c7 c7 [ 4616.167567] RSP: 0018:ffffaab88cbffca8 EFLAGS: 00010246 [ 4616.173406] RAX: ffff9ba1f9e44678 RBX: 0000000000000000 RCX: ffff9ba1c9792080 [ 4616.181376] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9ba1c9792080 [ 4616.189345] RBP: 0000000000000cc0 R08: ffffaab88cbffd10 R09: 0000000000000000 [ 4616.197317] R10: 0000000000000012 R11: 0000000000000000 R12: 0000000000000000 [ 4616.205288] R13: 0000000000400000 R14: 0000000000000cc0 R15: ffff9ba1c9792080 [ 4616.213259] FS: 00007f9a5534e980(0000) GS:ffff9ba1b7c80000(0000) knlGS:0000000000000000 [ 4616.222298] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4616.228719] CR2: 000055a390a4c518 CR3: 0000000123e40006 CR4: 00000000001706e0 [ 4616.236689] Call Trace: [ 4616.239428] blkdev_issue_discard+0x52/0xb0 [ 4616.244108] blkdev_common_ioctl+0x43c/0xa00 [ 4616.248883] blkdev_ioctl+0x116/0x280 [ 4616.252977] __x64_sys_ioctl+0x8a/0xc0 [ 4616.257163] do_syscall_64+0x5c/0x90 [ 4616.261164] ? handle_mm_fault+0xc5/0x2a0 [ 4616.265652] ? do_user_addr_fault+0x1d8/0x690 [ 4616.270527] ? do_syscall_64+0x69/0x90 [ 4616.274717] ? exc_page_fault+0x62/0x150 [ 4616.279097] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 4616.284748] RIP: 0033:0x7f9a55398c6b
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In Linux kernel md/raid0 and raid10, incorrect max_discard_sectors setting causes discard warnings on rotational disks.
Vulnerability
Overview
In the Linux kernel, the md (multiple device) drivers for RAID0 and RAID10 incorrectly set the max_discard_sectors parameter for the request queue. Instead of relying on disk_stack_limits to derive a proper value from the underlying member devices, the drivers directly assigned a value. This leads to a mismatch when all member disks are rotational (non-SSD/NVMe), as the RAID array exports a discard sector limit that is not supported by the hardware.
Exploitation and
Trigger
The vulnerability is triggered during filesystem operations that issue discard requests, such as mkfs.xfs. When the block layer processes a discard command via __blkdev_issue_discard, it validates the request against the queue's max_discard_sectors. Because the RAID driver set an inappropriate value, the kernel emits a warning message (as shown in the description's call trace) and the discard operation may fail or behave unexpectedly. No special privileges are required beyond the ability to create or use a RAID0/RAID10 array with rotational disks and issue discard commands.
Impact
An attacker with local access could potentially cause a denial of service by repeatedly triggering the warning, filling system logs, or causing filesystem operations to fail. The warning itself indicates a kernel bug that may lead to data corruption if discard operations are mishandled. However, the primary impact is operational instability and unexpected behavior during filesystem creation or maintenance.
Mitigation
The fix is included in the Linux kernel stable tree via commit [1]. Users should update to a kernel version containing this patch. The commit replaces the direct assignment of max_discard_sectors with a call to disk_stack_limits, ensuring the discard limit correctly reflects the capabilities of the underlying member devices. No workaround is available other than avoiding the use of discard operations on affected RAID arrays until the patch is applied.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
3e80bef07069927e5d61a8e698e1a2279ca2bVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
3News mentions
0No linked articles in our index yet.