7 matches found
CVE-2026-80733
A flaw was found in the Linux kernel's networking component. When processing network packets via raw or packet sockets over virtual devices, the skmcloop function could incorrectly trigger a WARNONONCE message. This occurred because the function did not properly handle non-INET Internet Protocol...
CVE-2026-53319
Mode C: Normal (details available) CVE-2026-53319 affects the Linux kernel block writeback throttling (blk-wbt) code. The issue arises in wbt_init_enable_default(), which previously used WARN_ON_ONCE to report failures from wbt_alloc() and wbt_init(). These failure paths are expected: wbt_alloc()...
CVE-2026-53319
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...
CVE-2026-53319
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...
CVE-2026-53319 blk-wbt: remove WARN_ON_ONCE from wbt_init_enable_default()
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...
EUVD-2023-60144
In the Linux kernel, the following vulnerability has been resolved: nvme-core: fix memory leak in dhchapsecretstore Free dhchapsecret in nvmectrldhchapsecretstore before we return fix following kmemleack:- unreferenced object 0xffff8886376ea800 size 64: comm "check", pid 22048, jiffies 4344316705...
Astra Linux - vulnerability in linux-6.1
In the Linux kernel, the following vulnerability has been resolved: iouring/tctx: workaround for the xastore allocation error issue syzbot triggered the following WARNON: WARNING: CPU: 0 PID: 16 at iouring/tctx.c:51 iouringfree+0xfa/0x140 iouring/tctx.c:51 which is the WARNONONCE!xaempty&tctx-xa;...