CVE-2026-53319
Last modified
CVE-2026-53319 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 7.0, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53319?
How severe is CVE-2026-53319?
How do I fix CVE-2026-53319?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53313In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53314In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53315In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53316In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53317In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53318In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5332A vulnerability was identified in Xiaopi Panel 1.0.0. This v…6.1
- CVE-2026-53320In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53321In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53322In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53323In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53324In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53319?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
