CVE-2026-53319 Details
Description
In the Linux kernel, the following vulnerability has been resolved: blk-wbt: remove WARN_ON_ONCE from wbt_init_enable_default() wbt_init_enable_default() uses WARN_ON_ONCE to check for failures from wbt_alloc() and wbt_init(). However, both are expected failure paths: - wbt_alloc() can return NULL under memory pressure (-ENOMEM) - wbt_init() can fail with -EBUSY if wbt is already registered syzbot triggers this by injecting memory allocation failures during MTD partition creation via ioctl(BLKPG), causing a spurious warning. wbt_init_enable_default() is a best-effort initialization called from blk_register_queue() with a void return type. Failure simply means the disk operates without writeback throttling, which is harmless. Replace WARN_ON_ONCE with plain if-checks, consistent with how wbt_set_lat() in the same file already handles these failures. Add a pr_warn() for the wbt_init() failure to retain diagnostic information without triggering a full stack trace.
A vulnerability in the Linux kernel's writeback throttling (WBT) component has been addressed. The issue arose because the function 'wbt_init_enable_default()' used 'WARN_ON_ONCE' to report failures from 'wbt_alloc()' and 'wbt_init()'. These failures were expected: 'wbt_alloc()' can return NULL due to memory pressure, and 'wbt_init()' can fail if WBT is already registered. This vulnerability was triggered by 'syzbot', which injected memory allocation failures during the creation of MTD partitions, leading to unnecessary warnings. The 'wbt_init_enable_default()' function is a best-effort initialization called from 'blk_register_queue()'. If it fails, the disk simply operates without writeback throttling, which is not harmful. The warning has been replaced with standard if-checks, aligning with how similar functions in the same file manage failures. Additionally, a 'pr_warn()' has been added for 'wbt_init()' failures to keep diagnostic information without causing a full stack trace.
Users can update to the latest version of the Linux kernel, where this vulnerability has been fixed. Instructions for updating the kernel can be found in the official Linux documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/e9b004ff83067cdf96774b45aea4b239ace99a2f | kernel.org | Patch |
| https://git.kernel.org/stable/c/fd7a982657077469802594a5165bc30b9a55af70 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-617 | Reachable Assertion | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 7.0, < 7.0.10 |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 6, 2026 | Initial Analysis | [email protected] |
| Jun 26, 2026 | New CVE Received | kernel.org |