CVE-2026-53319: blk-wbt: remove WARN_ON_ONCE from wbt_init_enable_default()

Published Jun 26, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

blk-wbt: remove WARNONONCE from wbtinitenabledefault()

wbtinitenabledefault() uses WARNONONCE to check for failures from wbtalloc() and wbtinit(). However, both are expected failure paths:

- wbtalloc() can return NULL under memory pressure (-ENOMEM) - wbtinit() 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.

wbtinitenabledefault() is a best-effort initialization called from blkregisterqueue() with a void return type. Failure simply means the disk operates without writeback throttling, which is harmless.

Replace WARNONONCE with plain if-checks, consistent with how wbtsetlat() in the same file already handles these failures. Add a prwarn() for the wbtinit() failure to retain diagnostic information without triggering a full stack trace.

Affected Software

2 affected components
Linux Kernel
Linux Linux kernel>=7.0<7.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In blk-wbt, replace WARN_ON_ONCE with plain if-checks in wbt_init_enable_default() to match the void return type behavior of blk_register_queue() and avoid spurious warnings/stack traces while keeping best-effort initialization failure paths diagnostic via pr_warn().

    Linux kernel blk-wbt WARN_ON_ONCE usage in wbt_init_enable_default() = replace WARN_ON_ONCE with plain if-checks

Event History

Jun 26, 2026
CVE Published
via MITRE·07:41 PM
Data Sourced
via MITRE·07:41 PM
Description
Data Sourced
via NVD·08:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53319?

CVE-2026-53319 has a medium severity rating of 5.5 according to the CVSS 3.1 metrics.

2

What are the potential impacts of CVE-2026-53319?

CVE-2026-53319 can lead to a denial of service due to memory allocation failures in the Linux kernel.

3

How do I fix CVE-2026-53319?

To fix CVE-2026-53319, update your Linux kernel to a version that includes the patch addressing this vulnerability.

4

Is CVE-2026-53319 specific to certain versions of the Linux kernel?

Yes, CVE-2026-53319 affects multiple versions of the Linux kernel; users should verify their specific version's vulnerability.

5

What components are affected by CVE-2026-53319?

CVE-2026-53319 affects the block writeback throttling (blk-wbt) component in the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203